geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: XA support
Date Tue, 29 Nov 2005 17:59:15 GMT
>From your derby-specific rars it looks like I would have to do this:

1) Unzip one of the derby-specific rar and delete the derby-specific jar 
which is inside.

2) Write an MCF (as you said) which instantiates 

3) Edit the ra.xml file to name the new MCF class and presumably mention 
the same of xa data source class somewhere (where?)

4) Jar up the whole thing again.

Is that enough or am I missing something here?


Jeremy Boynes <>
11/28/2005 10:34 PM
Please respond to user

        Subject:        Re: XA support wrote:
> A driver-based connector cannot support XA?

The generic driver-based connector uses a java.sql.Driver to get a
java.sql.Connection which only supports local transactions; you can't
get the necessary XAConnection from a Driver.

The generic connector one fakes out XA so that the appserver thinks it
is there but in reality the database is using local transactions. To
actually use XA a bit more work is needed.

> I don't know know enough about the issue to understand what you mean. I 
> presume that you are
> stating that in the context of JCA, but that if I create the xa data 
> source myself then it does (I did, it does.)

The TranQL connector framework provides all the infrastructure needed to
bridge between JDBC (XADataSource) and the J2CA APIs. However, for each
JDBC implementation it needs to create and initialize the XADataSource
and this is database specific.

To support a new database you need to provide the framework with a
JavaBean that creates the driver-specific XADataSource and allows the
appropriate properties to be initialized. This is pretty trivial as you
can see from the Derby one here:

It's really just a bunch of property accessors.

To make this into a connector, you also need a ra.xml, here's the one
for Derby:

If you can provide equivalents for your MySQL driver as a patch to we'd be happy to add them to the project - it is
testing the different environments that is the largest challenge.



In compliance with applicable rules and regulations, Instinet
reviews and archives incoming and outgoing email communications,
copies of which may be produced at the request of regulators.
This message is intended only for the personal and confidential
use of the recipients named above.  If the reader of this email
is not the intended recipient, you have received this email in
error and any review, dissemination, distribution or copying is
strictly prohibited. If you have received this email in error,
please notify the sender immediately by return email and
permanently delete the copy you received.  

Instinet accepts no liability for any content contained in the
email, or any errors or omissions arising as a result of email
transmission. Any opinions contained in this email constitute
the sender's best judgment at this time and are subject to change
without notice.   Instinet does not make recommendations of a
particular security and the information contained in this email
should not be considered as a recommendation, an offer or a
solicitation of an offer to buy and sell securities.


View raw message