On Sat, Mar 3, 2012 at 8:05 PM, Luke Manner <lukeman...@gmail.com> wrote: > Hi, > I'm facing the same task. > > > > Claus Ibsen-2 wrote >> >> Its Spring Transaction manager which orchestrates the transaction. So >> look into how you can enlist your resource >> into a Spring TX manager. >> >> The <transacted> just ensure the that the processing of the message >> occurs in a Spring managed transacted (eg using a transaction >> template, and issue the work in a doInTransaction method). As well as >> the routing engine will run in synchronous mode due Spring TX manager >> need to run in the same TX to work properly. >> > > If I understood well, a Transaction Manager defined through Camel (/and > outside from my component/) is responsible of mantaining and managing > transaction. From this point point of view, I have not to face how to build > it. > But I've to attach my component to it in some way. > > What is not clear in my mind is how to do that, because "linked point" > between my component and Camel are only: > - endpoint creation (in which I have no refer to any TX manager) > - consumer and producer creation > - processor and exchange > and no one of them seems to have any kind of connection with the > transactional mechanism. > > Do you have any hint on this subject? > Any help will be very useful! >
Your consumer or producer may support transactions in some way, and thus they can enlist into a TX manager. For example a JMS consumer, or a JDBC producer etc. > Thanks in advance > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-features-and-falling-back-to-Camel-components-tp5525681p5534184.html > Sent from the Camel Development mailing list archive at Nabble.com. -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
