Yes, it should be possible to define a transaction manager for the data source and make the route transacted with that one. However in that case the database accesses may be committed before the JMS read is committed (so if the removal of the message from the JMS queue fails, the database calls will be committed anyway.
-----Original Message----- From: James Green [mailto:james.mk.gr...@gmail.com] Sent: Montag, 22. September 2014 14:00 To: users Subject: Is this route possible..? We want to consume from JMS and route the message through a set of Processors which may or may not invoke database calls via DAOs. Thing is, we want the database calls to be wrapped in a transaction, but we don't have an XA transaction manager so the JMS part ought to be excluded. Is this possible? Thanks, James
