[jboss-jira] [JBoss JIRA] Commented: (JBAS-3364) Support PROPAGATION_NESTED in JTA implementation

[ http://jira.jboss.com/jira/browse/JBAS-3364?page=comments#action_12366596 ] Mark Little commented on JBAS-3364: ----------------------------------- In order to support nested transactions you need a nested transaction-aware coordinator and nested transaction-aware participants. The latter is pretty critical because what a participant does when it's told to commit in a nested transaction is completely different to a top-level transaction. Such participants are tailored for the backend datasource. JBossTS provides a nested transaction-aware coordinator and some nested transaction-aware participants. Take a look at the TS manuals (Core Transaction Engine) and you'll see. However, XA doesn't support nested transactions. And while JTA doesn't prevent them, JEE does not allow them for this reason. It's a strange situation to be in, I know! There's no way you can support true nested transactions with XA, so JTA should really be fixed. JBossTS continues to support nested transactions through JTA because you can register non-XA resources with our JTA transactions through other APIs. But as far as TS is concerned it's doing as much as it can. The rest is up to the datasource providers: implement nested transaction participants and this should just work (tm). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira