Topic 5 :Transaction Management in Mule 4

Author : @sravanlingam
Reach out to me : www.sravanling...
Subscribe : / @sravanlingam
LinkedIn : www.linkedin.com/in/sravanlingam
#mule4 #mulesoft #mule #salesforce @salesforce @sravanlingam
~-~~-~~~-~~-~
Please watch: "Implement an API using Anypoint Code Builder #ACB @sravanlingam #mule4 #mulesoft #salesforce"
• Implement an API using...
~-~~-~~~-~~-~

[@MuleSoftTechZone]

There’s a slight mistake in the slide . Please see the description for
ALWAYS_JOIN below
The connector will always join the existing transaction. If there is no transaction, or if the current transaction is not compatible with the current operation, the operation will fail to execute.

[@bhuvanhanumanthu6232]

Simple and easy to understand, Thanks for the video.

[@chaithanyareddy8381]

where can we identify transaction type in HTTP ? you skipped that one

[@saagnikadhikary6582]

I think the "ALWAYS_JOIN" will throw an error if there is no transaction already in progress and not start a new one, as you've mentioned. Could you please check and update on this?

[@MuleSoftTechZone]

Thanks for highlighting
It was a slide error . Will be pinning the comment with the correct description

[@PolandDiary]

thanks for the information. I have one doubt,why you used try block also with Transaction management, what happen we use with out transaction management with try block and with transaction management with database. please answer to my question... waiting for your reply

[@user-tz9wq9rk6j]

can you please try XA also

[@varshaludhrani6754]

What's the difference between indifferent and none ?

[@Enigmatechphaneendra]

in type XA, there will be multiple transactions right?

[@MuleSoftTechZone]

Multiple resources running on multiple transactions yes