[
https://issues.apache.org/activemq/browse/CAMEL-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45874#action_45874
]
Hadrian Zbarcea commented on CAMEL-316:
---------------------------------------
Let's see if we can do anything about this one in 1.5.
I propose to:
* not change the api
* deprecate faults
* consider faults outputs (not camel exception) and
1. faults are outputs of java.lang.Exception subtype *always*
2. fault are outputs of any type, but have a header (say "camel-fault" = true)
to indicate their fault semantic
3. faults are of type exception *and* have the fault header
* on fault the pipeline is interrupted (faults do not get sent to next
processor)
* keep the current mechanism - handleFault() - to handle faults as exceptions,
in which case faults become exceptions and the error handler applies.
We could then remove the fault api in 2.0. I'd love some feedback on this one.
> Merge Fault and Exception semantics
> -----------------------------------
>
> Key: CAMEL-316
> URL: https://issues.apache.org/activemq/browse/CAMEL-316
> Project: Apache Camel
> Issue Type: Improvement
> Reporter: Hadrian Zbarcea
> Assignee: Hadrian Zbarcea
> Fix For: 2.0.0
>
>
> The fact that there are output/fault/exception could be confusing and clutter
> the dsl, especially for components where there is no distinction between
> fault and exception. We should merge the two and simplify the model.
> See nabble thread:
> http://www.nabble.com/in-out-fault-messages-discussion-to14170013s22882.html#a14170013
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
