The dead letter endpoint can just be another route, and then use the direct component to send to that route. And in the route you can enrich the message with the details you want, before sending to the actual dead letter channel.
On Mon, Aug 5, 2013 at 9:47 AM, Darwish <othman.darw...@progressoft.com> wrote: > Hi , > > I wonder if it possible for camel to add custom property or header on the > message that exhausted all redelivery retries and moved to dead letter > queue > > This property may contain serialized version of the exception that lead > moving that message to dead letter queue > > This property will be very helpful– for me at least - when processing those > dead letter queue messages and usually creating NAK messages > > My current alternative option for creating such NAK message is to handle > those exceptions in each route > > Please advice > > > > ----- > Othman Darwish > ProgressSoft Corp. > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Promoting-the-exchange-message-cause-exception-as-property-or-header-when-moving-it-to-dead-letter-qe-tp5736778.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
