[
https://issues.apache.org/activemq/browse/CAMEL-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46302#action_46302
]
hadrian edited comment on CAMEL-960 at 10/9/08 9:51 PM:
----------------------------------------------------------------
@Claus, but that is already possible today (with the exception of the
failureHandled() api). What you added to my comment is that you want it
explicit, not implicit. Correct? (I am on irc, btw)
One more question. If you want it explicit what should the default be? If
it's handled by onException() should we throw the RuntimeCamelException by
default (if failureHandled(boolean) is not invoked) or consider it handled?
RE: BTW: The fix should be in restoreExceptionOnExchange in DeadLetterChannel.
Right, but i thought about not invoking restore... at all if this code above
was executed (i.e. processor is not null) and there is no other exception:
{code}
if (processor != null) {
data.failureProcessor = processor;
}
{code}
was (Author: hadrian):
@Claus, but that is already possible today (with the exception of the
failureHandled() api). What you added to my comment is that you want it
explicit, not implicit. Correct? (I am on irc, btw)
One more question. If you want it explicit what should the default be? If
it's handled by onException() should we throw the RuntimeCamelException by
default (if failureHandled(boolean) is not invoked) or consider it handled?
> 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.
