You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2009/08/24 09:47:50 UTC
[jira] Updated: (CAMEL-1929) doCatch handled(true) should have
access to caused exception just as onException has
[ https://issues.apache.org/activemq/browse/CAMEL-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen updated CAMEL-1929:
-------------------------------
Summary: doCatch handled(true) should have access to caused exception just as onException has (was: ErrorHandler - handling exception using handled=true should expose a flag its handled)
> doCatch handled(true) should have access to caused exception just as onException has
> ------------------------------------------------------------------------------------
>
> Key: CAMEL-1929
> URL: https://issues.apache.org/activemq/browse/CAMEL-1929
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.6.1, 2.0-M3
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.1.0
>
>
> When using
> {code}
> onException(Exception.class).handled(true).process(new MyErrorHandler());
> // or use
> doTry()
> ...
> doCatch(Exception.class).handled(true).process(new MyErrorHandler());
> {code}
> We should make it consistent that you can obtain the caused exception.
> So these properties on the Exchange should be the during the failure processor routing and what is returned to the client
> - Exchange.EXCEPTION_CAUGHT contains the caused exception
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.