camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Created: (CAMEL-960) DeadLetterChannel - option to mark the exchange as failure handled and that its OK
Date Mon, 06 Oct 2008 07:19:52 GMT
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: Claus Ibsen
             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.


Mime
View raw message