Amila, AFAIK there is only a single requirement to make the JMS transport work with JTA, namely that there is a connection factory which participates in distributed transactions and which can be looked up using JNDI. This is something that should also be provided by standalone JTA implementations.
Andreas On Wed, May 20, 2009 at 07:09, Amila Suriarachchi <[email protected]> wrote: > hi, > > I am trying to write a sample code using JMS transport to send a message > reliably from application to application. > > At the client side, > Axis2 client should be able to update a database and write to a jms queue in > a same distributed transaction and > > At the server side > it should be able to read the message from jms transport and update a data > base in a same distributed transaction. > > > Here I am planing to use a standalone jta implementation like atomikos[1] or > bitronix[2]. > > As I saw current JMS transport do support JTA. But As I saw it is required > to use a Application container (eg. jboss) > which has inbuilt JTA support. Is this correct or is there are a way to > configure standalone libraries. > > When Axis2 point of view people run the client in a stanalone applications > and server most of the time in tomcat. So it is usefull to have > support these standalone libraries as well. > > thanks, > Amila. > > > [1]http://www.atomikos.com/Main/ProductsOerview#ate > [2]http://docs.codehaus.org/display/BTM/Home > -- > Amila Suriarachchi > WSO2 Inc. > blog: http://amilachinthaka.blogspot.com/ >
