I'm not sure if LRCO solves the problem. What we need is to have the non-XA (in an XA wrapper) to perform its commit (prepare and commit for the wrapper) at the end of phase 1. This means that it is the last resource for phase 1 but the first resource for phase 2. This way, the resource can behave like a 1-phase commit, since it's performing both phases before any other resources start their phase 2.
Ideally, JBoss would allow one non-XA resource to participate in the distributed transaction. Websphere refers to this as "Last Participant": From: http://www-306.ibm.com/software/awdtools/studiointegration/about/simplify.html anonymous wrote : Last participant support provides automated coordination for transactions that include two-phase commit resources and a single one-phase commit resource. This support eliminates hand coding in this scenario and allows you to include one-phase commit resources, common for many legacy and package applications, in real transactions. SunOne implements Last Participant in the way I mentioned above. As long as you don't register more than one non-XA resource, the transaction will be XA. If you try to register a second one, it throws an exception. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3822029#3822029 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3822029 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
