camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5456) Context scoped exception clauses incorrectly applying across RouteBuilders
Date Sat, 29 Sep 2012 13:06:08 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-5456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13466223#comment-13466223
] 

Claus Ibsen commented on CAMEL-5456:
------------------------------------

Yes this issue is related to Java DSL. It has a slightly different initialization logic than
XML DSL etc.


                
> Context scoped exception clauses incorrectly applying across RouteBuilders
> --------------------------------------------------------------------------
>
>                 Key: CAMEL-5456
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5456
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.10.0
>            Reporter: Andreas Jacobsen
>            Assignee: Claus Ibsen
>         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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message