This content has been marked as final.
Show 3 replies
-
1. Re: 3.0 Beta Transacted Session Problem
pra Mar 21, 2002 10:53 AM (in response to feuxeu77)If you plan to use the XA-version of the connector you must manage your XA enrollment yourself, which is hairy and probably not allowed in an EJB.
If you want JMS to be part of the transactional context you MUST use the JMS ra, documented in the manual.
//Peter -
2. Re: 3.0 Beta Transacted Session Problem
feuxeu77 Mar 21, 2002 11:02 AM (in response to feuxeu77)What is the JNDI name for the RA ?
-
3. Re: 3.0 Beta Transacted Session Problem
feuxeu77 Mar 21, 2002 11:09 AM (in response to feuxeu77)Ok, thanks. I have found the JNDI name for the RA. It was "ConnectionFactory"
Thanks a lot.
I use JMS to alert clients when a modification occurs on an Entity Bean. It's better than my old technique which was the use of an UDP socket.