tag:blogger.com,1999:blog-8686578724458335326.post8322512078339510454..comments2023-10-30T09:15:49.715+00:00Comments on Narayana team blog: Nested transaction supportMark Littlehttp://www.blogger.com/profile/15072917010265365428noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8686578724458335326.post-12105962850195059782020-01-07T04:12:59.022+00:002020-01-07T04:12:59.022+00:00your blog has amazing content i was searching on t...your blog has amazing content i was searching on this topic and found your blog.i have bookmarked your blog please keep updating your content .we are providing <a href="http://twincitiestc.net/" rel="nofollow">Transaction Coordinators Services</a>twincitieshttps://www.blogger.com/profile/18347389938836406112noreply@blogger.comtag:blogger.com,1999:blog-8686578724458335326.post-75683164674071642862009-03-19T19:38:00.000+00:002009-03-19T19:38:00.000+00:00Mark,Good point: XA is not for nested transactions...Mark,<BR/><BR/>Good point: XA is not for nested transactions since you either allow shared branches (lock inheritance) at the expense of subtransaction rollback isolation, or you use different branches for each subtransaction - thereby making lock inheritance impossible!<BR/><BR/>So I agree with your point on a developer framework that defeats the limitations of JTA/XA - it is also what we at Atomikos have been doing :-)<BR/><BR/>Cheers<BR/>Guy<BR/>www.atomikos.comAnonymousnoreply@blogger.com