Would be possible for an HLF transaction to handle several proposals from different chaincode ?

Hello,

while our project is growing and we're integrating some external features we have some case where our business transaction atomicity would need some new feature from Hyperledger Fabric so that the HLF transaction atomicity would reflect the the business one.

Some context :

- we started with a feature involving a chaincode A. So our business transaction is mapping the technical transaction :

Prepare TX with chaincode A @ channel
if OK Broadcast TX

- then we had to integrate a new external feature to our business logic with a chaincode coming from another party. In the current state of the art of HLF as we know it, that means some happy path like this :

Prepare TX1 with chaincode A @ channel
if OK then Prepare TX2 with chaincode B @ channel
if OK then Broadcast TX2
if OK then Broadcast TX1

Here is the happy path. We would need some other logic to handle the bad scenarios.

I was thinking maybe HLF could help us to build a TX like this :

Prepare TX with chaincode A @ channel
if OK Complete TX with chaincode B @ channel
if OK Broadcast TX

That would help us a lot and in the end that would provide some atomic feature a little the same way SQL or JMS is providing to us when we deal with multiple table or queue. Let me know if such feature could be implemented in Fabric or if you have other ideas...

Best,