Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <248262228.1238647714879.JavaMail.jira@brutus>
Date: Wed, 1 Apr 2009 21:48:34 -0700 (PDT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Resolved: (CAMEL-316) Merge Fault and Exception semantics
In-Reply-To: <15834292.1201891475578.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/activemq/browse/CAMEL-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-316.
-------------------------------

    Resolution: Won't Fix

We never got this addressed in Camel 2.0 timeframe.

If really needed we can address or look at it again in Camel 3.0 or later.


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