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

Hadrian Zbarcea commented on CAMEL-960:
---------------------------------------

@Claus, I think we agree on that.

[..] alter the restoreExceptionOnExchange method in DeadLetterChannel, to NOT 
set the exception, or removing the  FAILURE_HANDLED_PROPERTY property will lead 
to the same thing: at the end of the day we don't what the exception back in 
the exchange if failureHandled(true) was invoked during handling, right? 

I am just trying to avoid using extra headers.  Maybe reset the value of 
FAILURE_HANDLED_PROPERTY to null, and then check that in 
restoreExceptionOnExchange(), not sure yet what works best, but the idea is to 
not put the exception back in the exchange.  Agree?



> DeadLetterChannel - option to mark the exchange as failure handled and that 
> its OK
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-960
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-960
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Hadrian Zbarcea
>             Fix For: 1.5.0, 2.0.0
>
>
> Currently the DeadLetterChannel sets the orignal caused exception on the 
> exchange *after* it has been failure handled. We should support somekind of 
> option to enable/disable this feature. We could support:
> - option on the endpoint to set this for all exchanges
> - support a special header key that end-users can insert per exchange to be 
> more dynamic
> - maybe methods on Exchange to set this more easily
> - maybe some refinements in isFailureHandled() to cater for this
> And we should consider use a better keyname in the DLC where it stores the 
> original exception. 
> See nabble:
> http://www.nabble.com/JMS-%2B-Fault-td19778503s22882.html
> We might need to push this for Camel 2.0 but I think it is a feature that 
> end-users would need sooner.
> Any thoughts, please write here?

-- 
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