Yes cluas .. XA is evil , i will simplify my route design and make sure
that the JDBC operation is last step in my route
Christian ..thank you for sample .. im reviewing the jmsAndJdbc sample:
from("activemqTx:queue:transaction.incoming.one")
.transacted("PROPAGATION_REQUIRED_JMS")
.transacted("PROPAGATION_REQUIRED_JDBC")
.to("sql:UPDATE account SET balance = (SELECT balance
from account where name = 'foo') - # WHERE name =
'foo'?dataSourceRef=dataSource")
.to("sql:UPDATE account SET balance = (SELECT balance
from account where name = 'bar') + # WHERE name =
'bar'?dataSourceRef=dataSource")
.to("activemqTx:queue:transaction.outgoing.one");
there is two transaction manager JMS and JDBC in same route which is
something new for me :) and i think it should be considered before going to
XA option
-----
Othman Darwish
ProgressSoft Corp.
--
View this message in context:
http://camel.465427.n5.nabble.com/Transactions-and-Cache-Levels-tp5733618p5733657.html
Sent from the Camel - Users mailing list archive at Nabble.com.
