camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-4022) Issue using errorBuilderRef with the xml dsl
Date Mon, 06 Jun 2011 09:48:58 GMT


Claus Ibsen commented on CAMEL-4022:

I have added unit tests on trunk

That tests for <onException> with both context and route scoped error handlers. I cannot
reproduce the issue Hadrian reported in the initial comment of this JIRA ticket.

The test Hadrian created in r1130232 does neither reproduce it as its only a Java DSL test
(no XML DSL test as well) and it indicated another issue, which is what should happen if another
exception is thrown during processing onException. That is ticket CAMEL-4041.

> Issue using errorBuilderRef with the xml dsl
> --------------------------------------------
>                 Key: CAMEL-4022
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.7.1
>            Reporter: Hadrian Zbarcea
>            Assignee: Hadrian Zbarcea
>            Priority: Critical
> While fixing issues around the errorHandler I noticed that <onException> definitions
defined in the camel context are ignored if a route specifies its own errorHandlerRef. The
reason is that we set the onException definition on the default error handler. I have a fix
for that, but I discovered a different issue (I think) for which I would like to discuss the
> When we have an onException definition that looks kinda like this:
> {code}
> <onException>
>   <exception> java.lang.IllegalArgumentException</exception>
>   <to uri="mock:illegalArgumentException"/>
> </onException>
> {code}
> ... something happens, the IAE exception is caught, we do something, but in that process
another exception is thrown. Currently, that would be caught by the default error handler,
which may not be what we want.
> What error handler (if any) should handle exceptions thrown while in onException?
> The onException mechanism is somewhat similar to a try/catch. I don't think the exceptions
thrown while handling onException should be handled by the same error handler configured for
the route, or even the context scoped one. The processing should be very simple, predictable
and immutable. Since the default "CamelDefaultErrorHandlerBuilder" can be replaced, it is
not imho a solution and we need one global one that does as little as possible (the problem
would be agreeing what that is: no redeliveries, logging or not, etc).
> Thoughts?

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message