Re: Cross chaincode invoke, ACL policy problem (MSP not defined in called channel, but in caller) #fabric-chaincode
From what I understand, only "query" (read only) transactions work cross-invoking in different channels.
If state is modified by chaincode, then channel has to be same as callers chaincode.
In the example, if chaincodeB is invoking chaincodeA, can chaincodeA be deployed in channel-2 ?
On Tuesday, June 22, 2021, 04:34:16 PM GMT+5:30, Sergio C <schica@...> wrote:
Org4.member invokes (query) chaincodeB (in Org3Peer) in channel-2 (ok, because Org4 is in channel-2), then chaincodeB internally invokes (query) chaincodeA (fails, because Org4Member MSP isn't defined in channel-1).
Is it possible to bypass this problem?