[
https://issues.apache.org/activemq/browse/CAMEL-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45922#action_45922
]
Hadrian Zbarcea commented on CAMEL-316:
---------------------------------------
The only difference between #1 and #3 is the header. Assuming that normal
outputs cannot be of java.lang.Exception type, which is I think pretty
reasonable, there is no difference between the two. I have however an
amendment for #3:
#4. faults are of type java.lang.Exception and a header CamelFaultOrigin=<url>.
The header's mere presence is equivalent with CamelFault=true, as proposed in
#3, but also gives a hint of what endpoint produced the fault. We may need
more details about the fault.
> 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.
