Hi Transactions only works for a limited number of components. You cannot rollback a file deletion etc.
On Tue, May 25, 2010 at 12:05 PM, ankelee <andreasasm...@gmail.com> wrote: > > Hi > > I'm trying to figure out what transactions can do for me. > > I'm wondering if transactions can be set up to also handle side-effects of > the route. I would like to roll back the file that is sent to the wireTap. > Alternatively I would have to go back and delete it manually using > errorhandling in case the route fails. > > Also, let's say that SomeProcessor deletes a file, is it possible to setup > something to deal with rolling back that deletion also? > > <route id="InboundRoute"> > <from uri="file:data/in/inbox?delay=5000" /> > <transacted /> > <wireTap uri="file:data/in/backup" /> > <from uri="direct:EvaluateAckRequest" /> > <to uri="SomeProcessor" /> > <to uri="jms:Input" /> > </route> > > Are transactions even relevant in a route like this, or should I just be > using normal errorhandling and clean up myself. Since Camel already rolls > back a file on error, is there any point in transactions in this case? > > -- > View this message in context: > http://old.nabble.com/Transactions-in-File-to-JMS-route.-tp28666530p28666530.html > Sent from the Camel - Users mailing list archive at Nabble.com. > > -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus