4 Replies Latest reply on May 21, 2002 10:21 PM by pylet

    mySQL and XADataSource

    jgeisler
    jgeisler May 16, 2002 5:40 AM

      Since version 2.0.11 or so the mm.mysql JDBC driver supports the XADataSource interface. Now I wonder if I could write a mysql-service.xml file to setup a resource adapter with full XA transaction support for mySQL. If this is possible, how would it have to look like and would I benefit from it as opposed to only having LocalTransaction support with the current resource adapter setup for mysql that is shipped with jboss?

      Thanx for help
      Jens

      • 3076 Views
      • Tags:
        • 1. Re: mySQL and XADataSource
          davidjencks
          davidjencks May 16, 2002 9:06 AM (in response to jgeisler)

          If you look closely, you will find that the mysql "xa" is a fake xa wrapper with no xa semantics. I think it's simpler to stick with the local wrapper where we know the sharing is appropriate within one transaction.

            • Actions
          • 2. Re: mySQL and XADataSource
            jgeisler
            jgeisler May 18, 2002 4:13 PM (in response to jgeisler)

            I just wondered if LocalTransaction means that if I have all my EntityBeans in one DBMS that transactions are fully supported.
            Jens

              • Actions
            • 3. Re: mySQL and XADataSource
              davidjencks
              davidjencks May 18, 2002 10:12 PM (in response to jgeisler)

              As long as you don't include other things like transacted jms messages in the same transaction you will be fine. If you only use mysql local transactions are adequate.

                • Actions
              • 4. Re: mySQL and XADataSource
                pylet
                pylet May 21, 2002 10:21 PM (in response to jgeisler)

                > If you look closely, you will find that the mysql
                > "xa" is a fake xa wrapper with no xa semantics.

                Yes, as MySQL doesn't support XA (yet, I'm pushing for it). This XADataSource implementation was meant to be used where there were no other options, which is not the case in JBoss.


                  • Actions