Hi There is a difference in *transaction client EIP* and the *dead letter channel* EIP
Transactional Uses true transactions using commit/rollback so the operations is all or nothing. This is handled 100% *not* by Camel but by the backing external system (the transaction manager). Only some transports support transaftions such as: JMS, JDBC etc. So if you want to rollback on the JMS topic then you need transactions and to use the transaction manager from the JMS broker. Dead Letter Channel Does *not* use transactions but will retry the step in the routing that failed. This is handled 100% by Camel. /Claus Ibsen Apache Camel Committer Blog: http://davsclaus.blogspot.com/ On Fri, Dec 5, 2008 at 8:52 PM, dougly <[EMAIL PROTECTED]> wrote: > > Hi, > I have the following route: > > from("jms:topic:example").process(new MyProcessor()); > > If during the exchange processing exceptions are thrown, I would like to be > able to retry that exchange again. > > I am thinking about using the Transactional client described in EIP but also > I find out that Dead Letter Channel has the redelivery mechanism to achieve > the same thing. > > So experts, in this case should I just use the Dead Letter channel > redelivery to shift the exchange back to the JMS topic for another try? > > Thanks > > Doug > -- > View this message in context: > http://www.nabble.com/Redilivery-Strategy-tp20861316s22882p20861316.html > Sent from the Camel - Users mailing list archive at Nabble.com. > >
