Hey Mark, Your code is really clean and nice, that's really good start for others. I am happy that you managed XA to work. However for one JMS and one JDBC resource you need only a local transaction. If the JDBC operation is in JMS transaction bounds you can rely on it. I am in middle of writing blog post about that.
Best regards, Łukasz Dywicki -- Code-House http://code-house.org Wiadomość napisana przez MarkS1900 w dniu 2012-01-28, o godz. 23:15: > I think I managed to get JTA/XA transactions using the default ServiceMix > 4.4.0 with Atomikos. > > The example I created contains a Java Service Bean making JMS and JDBC > calls, and multiple Camel Routes making JMS and JDBC calls. > > Source location: > https://bitbucket.org/mark1900/test-osgi > > > The OSGi Blueprint configuration lives here: > https://bitbucket.org/mark1900/test-osgi/src/d536e2161ee4/test-osgi-blueprint-xa-atomikos/src/main/resources/OSGI-INF/blueprint > > README location: > test-osgi/test-osgi-blueprint-xa-atomikos/README.txt > > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/JTA-XA-transactions-using-the-default-ServiceMix-4-4-0-features-install-transaction-tp5434170p5438693.html > Sent from the ServiceMix - User mailing list archive at Nabble.com.
