Hi Sidney,
Apologies for the delay.
Typically the container that you use is responsible for
enlisting a resource. Basically a resource adapter (or a
JMS client library) provides an XAResource object and
the container enlist it. Normally user application doesnt
have to worry about that.
If you use a TM yourself, you might have to do the explicit enlistment.
Ideally I would assume that the container would shield how
a resource is enlisted in TM from user.
GRA does support distributed transactions for any XA
capable jms provider.
I dont know Spring well enough to explain you how
Spring make use of this capability. But we know that Jenks folks
have tried out genericjmsra and google search reveal
some examples also.
Did you ask this question in Spring forums?
thanks,
Binod.
>I
>have a Spring application that uses a JMS and Database
>resouces. Because of that we need to use XA. At this
>point we are testing JOTM. I was able to get a
>prototype working with Spring, JOTM, Mysql, and Sonic.
>However, I have to manually enlist the XAResource
>coming out of the JMS XASession. And I was wondering
>if by using the Generic Resource Adapter for JMS, I
>could avoid doing this and have the resouce manage
>that for me.
>
>Thank you in advance.
>
>Sidney
>
>
>
>____________________________________________________________________________________
>The fish are biting.
>Get more visitors on your site using Yahoo! Search Marketing.
>http://searchmarketing.yahoo.com/arp/sponsoredsearch_v2.php
>
>