Are the still using that thing? Are you in Buedelsdorf?
-Andy
On 9/12/03 9:31 AM, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
For consistent updates of multiple resources we need XA transactions. Unfortunately some of our resources (e.g. MySQL DB or SAP R/3 JCA Connector, so it should be a quite common issue) only support local transactions ( meaning no 2-phase commit ).
Nevertheless consistent updates between multiple XA transaction resources and ONE local transaction resources should be still be possible if the transaction manager succesfully commits the changes to the local transaction resource AFTER succesfull preparation of all XA transaction resources (phase 1 of 2-phase-commit). In case of commit failure of the one local transaction resource all XA resources still could be rolled back to their previous state by dropping phase 2 XA commit operation.
Is this supported by the JBOSS transaction manager ? I kown that local transaction resources can be enlisted in an XA transaction ( with a warning message like "Local connection enlisted in global xa transaction. You may get results you are not expecting !")
Any information on the issue would be appreceated.
Regards
Ulf
--
Andrew C. Oliver
http://www.superlinksoftware.com/poi.jsp
Custom enhancements and Commercial Implementation for Jakarta POI
http://jakarta.apache.org/poi
For Java and Excel, Got POI?
The views expressed in this email are those of the author and are almost definitely not shared by the Apache Software Foundation, its board or its general membership. In fact they probably most definitively disagree with everything espoused in the above email.
