AFAIK this is not supported, because transactions are threadbound and the SEDA stuff will run of another thread than the one that started the transaction, and hence not able to participate in it.
2014/1/16 gilboy <[email protected]> > Hi > > I have a route to consume a message from a JMS Topic, do some processing on > it and then place on a SEDA Queue. > > My second route will consume the message from the SEDA queue and place on a > different JMS Topic. > > I want to ensure that the message only gets de-queued from the first Topic > which it has successfully been placed on the 2nd topic. Is this possible? > > Thanks in advance > Joe > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Transaction-spanning-multiple-routes-separated-by-seda-queue-tp5746041.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- -- David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
