Return-Path: Delivered-To: apmail-geronimo-user-archive@www.apache.org Received: (qmail 71245 invoked from network); 29 Nov 2005 16:49:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Nov 2005 16:49:51 -0000 Received: (qmail 46472 invoked by uid 500); 29 Nov 2005 16:49:47 -0000 Delivered-To: apmail-geronimo-user-archive@geronimo.apache.org Received: (qmail 46452 invoked by uid 500); 29 Nov 2005 16:49:46 -0000 Mailing-List: contact user-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: user@geronimo.apache.org List-Id: Delivered-To: mailing list user@geronimo.apache.org Received: (qmail 46441 invoked by uid 99); 29 Nov 2005 16:49:46 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Nov 2005 08:49:46 -0800 X-ASF-Spam-Status: No, hits=0.6 required=10.0 tests=HTML_MESSAGE,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [198.178.41.151] (HELO bedmsw02.esn.instinet.com) (198.178.41.151) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Nov 2005 08:51:14 -0800 Received: from hmtalz01.prod.instinet.com (unverified) by bedmsw02.esn.instinet.com (Content Technologies SMTPRS 4.3.17) with ESMTP id for ; Tue, 29 Nov 2005 11:41:03 -0500 Received: from hfccldmmail001.isn.instinet.com (hfccldmmail001.isn.instinet.com [172.27.134.25]) by hmtalz01.prod.instinet.com (8.12.8/8.12.8) with ESMTP id jATGiLrC030853 for ; Tue, 29 Nov 2005 11:44:22 -0500 To: user@geronimo.apache.org Cc: user@geronimo.apache.org Subject: Re: XA support MIME-Version: 1.0 X-Mailer: Lotus Notes Release 5.0.12 February 13, 2003 Message-ID: From: Guglielmo.Lichtner@instinet.com Date: Tue, 29 Nov 2005 08:45:42 -0800 X-MIMETrack: Serialize by Router on NYMAIL1/US/INSTINET (Release 6.5.4FP2|September 12, 2005) at 11/29/2005 11:45:44 AM, Serialize complete at 11/29/2005 11:45:44 AM Content-Type: multipart/alternative; boundary="=_alternative 005BE470882570C8_=" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multipart message in MIME format. --=_alternative 005BE470882570C8_= Content-Type: text/plain; charset="us-ascii" I just remembered that the latest release of mysql connector/j does not support xa. I am using an alpha version, which at first was coded incorrectly (and I believe never tested) but it was a small bug and I was able to fix it. So you'd be supporting an alpha driver. That's probably the reason why you don't support xa for mysql. Jeremy Boynes 11/28/2005 10:34 PM Please respond to user To: user@geronimo.apache.org cc: Subject: Re: XA support Guglielmo.Lichtner@instinet.com 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: http://cvs.tranql.codehaus.org/vendors/derby/common/src/java/org/tranql/connector/derby/ClientXAMCF.java?rev=1.2&view=auto 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: http://cvs.tranql.codehaus.org/vendors/derby/client-xa/src/rar/META-INF/ra.xml?rev=1.1&view=auto If you can provide equivalents for your MySQL driver as a patch to dev@tranql.codehaus.org we'd be happy to add them to the project - it is testing the different environments that is the largest challenge. -- Jeremy ***************************************************************** <<>> 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. ***************************************************************** --=_alternative 005BE470882570C8_= Content-Type: text/html; charset="us-ascii"
I just remembered that the latest release of mysql connector/j does not support xa.
I am using an alpha version, which at first was coded incorrectly (and I believe never tested)
but it was a small bug and I was able to fix it.

So you'd be supporting an alpha driver. That's probably the reason why you don't support xa for mysql.



Jeremy Boynes <jboynes@apache.org>

11/28/2005 10:34 PM
Please respond to user

       
        To:        user@geronimo.apache.org
        cc:        
        Subject:        Re: XA support



Guglielmo.Lichtner@instinet.com 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:
http://cvs.tranql.codehaus.org/vendors/derby/common/src/java/org/tranql/connector/derby/ClientXAMCF.java?rev=1.2&view=auto

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:
http://cvs.tranql.codehaus.org/vendors/derby/client-xa/src/rar/META-INF/ra.xml?rev=1.1&view=auto

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

--
Jeremy



*****************************************************************
<<>>

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.

*****************************************************************
 --=_alternative 005BE470882570C8_=--