On Tue, Jul 16, 2013 at 9:48 AM, gquintana <gerald.quint...@gmail.com>wrote:
> Seda breaks transaction propagation since different threads are used. But > you > can replace seda by JMS > This applies when a Global TransactionManager is in place (e.g. JTA), whose typical way of synchronizing several atomic TXs is by following the thread and tracking which TXs are bound to that thread. That's why I specifically referred to non-XA transactions in my email ;-) When using local (non-XA) JMS transactions, Camel will use the UnitOfWork concept along with Synchronizations to commit/rollback the transaction when the Exchange is done. When using waitForReply=Always, the Exchange won't be done until the reply is received, and therefore the UoW won't complete until then. Regards, *Raúl Kripalani* Apache Camel PMC Member & Committer | Enterprise Architect, Open Source Integration specialist http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani http://blog.raulkr.net | twitter: @raulvk
