[jbossts-issues] [JBoss JIRA] Closed: (JBTM-485) Expose creation of WS-AT subtransactions and creation of associated WS-AT context to support JTA ==> WS-AT transaction bridging

[Andrew Dinn (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBTM-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Dinn closed JBTM-485.
----------------------------

    Resolution: Done


Fixed by revision 25158.

The 1.1 build or combined 1/1/1.0 build of jbossxts-api.jar included in the delivered sar archive now includes class org.jboss.jbossts.xts.bridge.at.BridgeWrapper which exposes all the required functionality.


> Expose creation of WS-AT subtransactions and creation of associated WS-AT context to support  JTA ==> WS-AT transaction bridging
> --------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBTM-485
>                 URL: https://jira.jboss.org/jira/browse/JBTM-485
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: WS-T Implementation
>    Affects Versions: 4.5
>            Reporter: Andrew Dinn
>            Assignee: Andrew Dinn
>             Fix For: 4.6
>
>
> Currently WS-AT subordinate transaction coordinators are only created when a transaction is activated from within an existing WS-AT transaction context. JTA ==> WS-AT bridging needs to be bale to pirate this functionality.
> During normal operation the bridge code needs to create and register a WS-AT subordinate coordinator when the bridge is first established. It also needs to be able to obtain a Tx Context for the transaction and to obtain the transaction id so it can log it in recovery records.
> At recovery time the bridge code needs to lookup a recovered subordinate transaction coordinator by transaction id. If no coordinator is found it needs to be able to determine whether this is because there is no record in the log or because the log has not been scanned yet. There is no requirement for the bridge code to be able to obtain a transaction context at recovery time.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira