The message that is send to the DLC is the message as it was just before the node which failed in the Camel route. So if exProcessor fails, then the message is the input for the exProcessor processor.
On Fri, Jan 14, 2011 at 9:47 PM, swwyatt <[email protected]> wrote: > > I have a route that uses a DeadLetterChannel error handler. After > unsuccessful retires, message is sent to the deadLetterUri which is a JMS > queue. The message that is enqueued is the original message that failed to > process in the route. How can I set this up so that the message that is sent > to the dead letter queue retains any modifications made to the message in > the route? Below is a sample of my setup. > > > <camel:camelContext id="test"> > <camel:errorHandler id="errorHandler" type="DeadLetterChannel" > deadLetterUri="errorSender:queue:errorQueue"> > <camel:redeliveryPolicy maximumRedeliveries="3" > redeliveryDelay="10000"/> > </camel:errorHandler> > <camel:route id="route1" errorHandlerRef="errorHandler"> > <camel:from uri="jms:queue:testQueue"></camel:from> > <camel:enrich uri="bean:exProcessor?method=getString" > strategyRef="exProcessor"></camel:enrich> > <camel:process ref="exProcessor"></camel:process> > <camel:to uri="file:c://temp"></camel:to> > </camel:route> > </camel:camelContext> > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Error-handler-and-original-message-tp3341901p3341901.html > Sent from the Camel - Users mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
