You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Bryan Brouckaert (JIRA)" <ji...@apache.org> on 2011/07/18 08:26:59 UTC

[jira] [Commented] (CAMEL-4234) ProducerTemplate/MockEndpoint does not seem to trigger context exception handling.

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

Bryan Brouckaert commented on CAMEL-4234:
-----------------------------------------

Hello,

It doesn't seem to be easy to replicate the issue, but I did get some extra information.

I do get the following log entry:
TRACE [org.apache.camel.processor.exceptionpolicy.DefaultExceptionPolicyStrategy] - The type is scoped for route: userWs.getUser however Exchange is at route: userWs.listUsers

Which explains why the onException isn't triggerd.  But what is strange, is that the onException is defined on context level and the route thas is executed is userWS.getUsers.

I'll include my routing config, and keep working on a simple example.

> ProducerTemplate/MockEndpoint does not seem to trigger context exception handling.
> ----------------------------------------------------------------------------------
>
>                 Key: CAMEL-4234
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4234
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.8.0
>         Environment: JUnit4 Spring tests, Spring DSL
>            Reporter: Bryan Brouckaert
>         Attachments: routes.xml
>
>
> Hello,
> I have a camel route that has "onException" clause.  When I run it on Tomcat it works pefectly, but in my integration test (JUnit4 + Spring Tests) the exception handling isn't triggered.  The unit tests uses a producer template and mock endpoint, so it seems that it is in one of those.
> I'll try to reproduce it in a small test case.
> Kind regards,
> Bryan. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira