[jbossts-issues] [JBoss JIRA] Closed: (JBTM-790) XTS demo should fully exercise latest recovery API
Andrew Dinn (JIRA)
jira-events at lists.jboss.org
Tue Sep 28 05:52:28 EDT 2010
[ https://jira.jboss.org/browse/JBTM-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Dinn closed JBTM-790.
The demo is now probably able to be used as an example in the user guide to explain in full how the BA and AT protocols can be used to drive a web service which employs a local transactional resource manager to store and update web service state. Modifying the XTS programmer's guide accordingly should be performed as a follow-up task.
This is all very well for those who want to understand the protocols but most users are likely just to want to employ an XA resource within either an AT or BA transaction so as to avoid writing i) the resource manager itself and ii) the participant classes which drive the resource manager. This can already be done for AT transactions using the AT-JTA bridge code. More work is still needed to make this work for BA transactions, in particular a way of identifying what the web service wants to do at complete, close, cancel and compensate. This will be addressed as part of the rewriting of the BA framework prototype.
So, once that has been done the other follow-up task to this one is to provide an alternative version of the demo where the AT and BA web services implement the same functionality but they use a local XA resource (e.g. a database) to provide the transactional storage and update of the booking data.
> XTS demo should fully exercise latest recovery API
> Key: JBTM-790
> URL: https://jira.jboss.org/browse/JBTM-790
> Project: JBoss Transaction Manager
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: XTS
> Affects Versions: 4.12.0
> Reporter: Andrew Dinn
> Assignee: Andrew Dinn
> Fix For: 4.13.0
> The XTS demo does not currently fully exercise the recovery API because it is faking modifying and persisting changes of web service state via a local transactional resource. This means it does not need to link the prepare and commit cycle for the local state to the progress of the encompassing AT or BA web service transaction. In particular the new API methods introduced as part of JBTM-786 are not being exercised. The demo should be updated to employ a simple local transactional resource and to drive this resource correctly using the new API.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbossts-issues