Actually I developed a sample application that uses XA transaction. In the sample a session bean first publishes two messages to a topic using XAConnectionFactory, latter it updates the DB using a entity bean. The entity bean also looks-up the connection from the XA datasource.
To test my sample application, I tried to throw exception in between publishing the message and the DB update. So now according to the XA transaction, both the things should fail. Now the application is working fine if I deploy the session bean as bean managed transaction (i.e with transaction-type to Bean). But the same sample application is not working when I deploy the session bean as container managed transaction (i.e with transaction-type to container) By working fine I mean to say that the message published does not reach the destination, once the exception is thrown. Can any one please help me in the regard. Also it will be greatfull if any one can point me to a working example using XA Transaction. Thank you View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3880401#3880401 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3880401 ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
