[ 
https://issues.apache.org/activemq/browse/CAMEL-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51621#action_51621
 ] 

Claus Ibsen commented on CAMEL-1600:
------------------------------------

Oh and as always {{onException}} could benefit as well. So lets add the option 
there as well, giving Camel end users the ultimate flexibility.

By default it will be _off_ in that sense it behaves as before. So you need 
explicit to enable it to use it.

> DeadLetterChannel - add option for moving the original exchange to the dead 
> letter queue instead of the current snapshot of the exchange
> ----------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1600
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1600
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 1.6.0, 2.0-M1
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.0.0
>
>
> Idea from an end user on the fuse forum:
> http://fusesource.com/forums/thread.jspa?messageID=2649&#2649
>     /**
>      * Will use the original input {...@link Exchange} when an {...@link 
> Exchange} is moved to the dead letter queue.
>      * <p/>
>      * <b>Notice:</b> this only applies when all redeliveries attempt have 
> failed and the {...@link Exchange} is doomed for failure.
>      * <br/>
>      * Instead of using the current inprogress {...@link Exchange} IN body we 
> use the original IN body instead. This allows
>      * you to store the original input in the dead letter queue instead of 
> the inprogress snapshot of the IN body.
>      * For instance if you route transform the IN body during routing and 
> then failed. With the original exchange
>      * store in the dead letter queue it might be easier to manually re 
> submit the {...@link Exchange} again as the IN body
>      * is the same as when Camel received it. So you should be able to send 
> the {...@link Exchange} to the same input.
>      * <p/>
>      * By default this feature is off.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to