[ https://jira.jboss.org/browse/JBTM-790?page=com.atlassian.jira.plugin.sys... ] Andrew Dinn commented on JBTM-790: ---------------------------------- The demo also ought to be modified so that it implements both a BA Participant Completion participant and a BA Coordinator Completion participant, providing a simple example of why one protocol would be chosen over the other. -- 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

[ https://jira.jboss.org/browse/JBTM-790?page=com.atlassian.jira.plugin.sys... ] Andrew Dinn closed JBTM-790. ---------------------------- Resolution: Done 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. -- 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