Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <1457350160.1238999794749.JavaMail.jira@brutus>
Date: Sun, 5 Apr 2009 23:36:34 -0700 (PDT)
From: "Claus Ibsen (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Resolved: (CAMEL-1518) Add method
 Exchange.getException(Type) - that will traverse the caused by tree and
 find the given type
In-Reply-To: <852269861.1238864974692.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-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-1518.
--------------------------------

    Resolution: Fixed

trunk: 762220

> Add method Exchange.getException(Type) - that will traverse the caused by tree and find the given type
> ------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1518
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1518
>             Project: Apache Camel
>          Issue Type: New Feature
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> Camel often wraps the real caused exception in wrapper exceptions such as
> - CamelExchangeException
> - RuntimeCamelException
> and what else is there
> We should support its easier to get the caused/expected exception in the exception tree using the type parameter on getException.
> Then drill down the tree and find the given exception.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.