camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Jacobsen (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5456) Context scoped exception clauses incorrectly applying across RouteBuilders
Date Wed, 22 Aug 2012 06:01:38 GMT


Andreas Jacobsen commented on CAMEL-5456:

It can't possibly be correct that route-context-scoped exception clauses are dependent on
the order of the routes they are tied to. That's insane. 
> Context scoped exception clauses incorrectly applying across RouteBuilders
> --------------------------------------------------------------------------
>                 Key: CAMEL-5456
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.10.0
>            Reporter: Andreas Jacobsen
>            Assignee: Willem Jiang
>         Attachments: camel-core-context-scope-bug.patch, camel-spring-context-scope-bug.patch
> The attached patch shows a bug in the DefaultExceptionPolicyStrategy or the way ExceptionPolicys
are added to a RouteBuilder's errorhandler.
> In ContextScopedOnExceptionMultipleRouteBuildersReverseTest, the ordering of the routes
causes the onException(IllegalArgumentException.class) to added to the ExceptionProcessors
for the direct:foo-RouteBuilder. When the route is run, the OnExceptionDefinition matches
exactly on the exception-type, despite this OnExceptionDefiniton being registered on a different
RouteBuilder. As far as we can tell, the processor is later ignored because it's identified
as being from a different route-context.
> We have attached corresponding tests for camel-spring that show that the issue is tied
to alphabetical ordering of RouteBuilders when using contextscan.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message