Hi
Glad you found a solution to your problem.
On Tue, Dec 9, 2008 at 6:53 PM, efender <[EMAIL PROTECTED]> wrote:
>
> Got it. I need to over write my "in" instead of setting my out. Works
> perfectly. Now my DLQ has complete knowledge of the original failed
> message, including Camel properties and JMS headers.
>
> public void process(Exchange exchange) throws Exception {
> Message in = exchange.getIn();
> Object body = in.getBody();
> DeadLetterWrapper wrapper = new DeadLetterWrapper();
> wrapper.setDeadLetter(body);
> wrapper.setHeaders(in.getHeaders());
> wrapper.setProperties(exchange.getProperties());
> in.setBody(wrapper);
> }
>
>
>
> efender wrote:
>>
>> Ok that didn't work. My DeadLetterPersistanceProcessor is still getting a
>> BlockUserRequest object instead of a DeadLetterWrapper. I swear it worked
>> at some point.
>>
>
> --
> View this message in context:
> http://www.nabble.com/Saving-original-destination-when-sending-to-DLQ-tp20914367s22882p20919910.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
/Claus Ibsen
Apache Camel Committer
Blog: http://davsclaus.blogspot.com/
