Hi If the insert/update into the DB is only one write operation and its the last in the route, then you can just use the JMS transactions. As if write to DB fails it will thrown an exception and cause the JMS to rollback.
If write success then no exception and the JMS can ack the message. If you have a copy of Camel in Action, then chapter 9 covers all about transaction and also this 1PC use-case, you talk about. And the Camel docs has a bit about TX too at http://camel.apache.org/transactional-client.html On Fri, May 30, 2014 at 5:18 PM, dancsi <andras_dancs...@epam.com> wrote: > I'm trying to implement/configure Best Efforts 1PC pattern for > "transactional" consuming of MQ (IBM/WepSphere) messages and > inserting/updating the DB (Oracle). > > Shall I use > org.springframework.jms.connection.TransactionAwareConnectionFactoryProxy > over the MQ connection factory with Spring data source tx manager to handle > the DB-side of the transaction? > Does transacted route configuration apply in this case? > > Thanks, > Dan > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Best-Efforts-1-PC-pattern-from-MQ-to-DB-tp5751757.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
