search

casualcore / casual

casual xatmi implementation
http://casual.laz.se
MIT License
7 stars 2 forks source link

transaction: make sure uses tightly coupled transaction on roundtrips between domains #5

Open albinsjolund opened 2 years ago

albinsjolund commented 2 years ago
OlofGullnas commented 2 years ago

This issue is bogus. I think it say that Casual should make sure that XID 1:1 should be used in domain A in the third step n the scenario. I do not THINK that is the way for example Tuxedo worked. There a new branch is used when coming back to the original domain after a "roundtrip". At least that is how I understand the Tuxedo documentation. See https://docs.oracle.com/cd/E13203_01/tuxedo/tux71/html/addoma9.htm.

Another issue is if/how to control loosely/tightly coupled transactions within a domain! The XA spec talks about loosely and tightly coupled transactions. So far I have not found anything in the XATMI spec or in tx.pdf on how to select between them at the AP level. In a Tuxedo domain separate groups seems to imply loosely coupled. In casual the service attribute "transaction: branch" causes a new transaction branch and loosely coupled transactions.