You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "James Strachan (JIRA)" <ji...@apache.org> on 2007/11/05 16:03:23 UTC

[jira] Resolved: (CAMEL-197) Processor invocation order

     [ https://issues.apache.org/activemq/browse/CAMEL-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Strachan resolved CAMEL-197.
----------------------------------

    Resolution: Fixed

fixed - see the test cases...
InterceptorBuilderTest and InterceptorBuilderWithEndTest


> Processor invocation order
> --------------------------
>
>                 Key: CAMEL-197
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-197
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 1.2.0
>            Reporter: Hadrian Zbarcea
>             Fix For: 1.3.0
>
>         Attachments: camel-interceptor-bug.patch
>
>
> Please see attached patch to reproduce.
> I made a small change to an existing unit test and created a route like this:
> from("direct:a").intercept(interceptor1).process(orderProcessor).intercept(interceptor2).to("direct:d"); 
> I think one would expect to have one route and the invocation order to be interceptor1 -> orderProcessor -> interceptor2 -> direct:d.
> Instead we have:
> 1. two routes
> 1. interceptor1 and interceptor2 are invoked twice
> 2. orderProcessor is never invoked
> 3. direct:d is invoked twice, i think.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.