Mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadrian Zbarcea (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-3928) custom interceptor - wrapProcessorInInterceptors - passing parent Description on Split
Date Mon, 02 May 2011 16:16:03 GMT

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

Hadrian Zbarcea commented on CAMEL-3928:
----------------------------------------

@Javier, thanks for the clarification. No worries then. We appreciate unit tests whenever
contributors provide them, otherwise, we have to write them ourselves to prevent the issue
from popping up again in a future release. I will assign this to me and provide a unit test.
It doesn't make your contribution any less important. Thanks again.

> custom interceptor - wrapProcessorInInterceptors - passing parent Description on Split
> --------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3928
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3928
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.2.0, 2.3.0, 2.4.0, 2.5.0, 2.6.0, 2.7.0, 2.7.1
>         Environment: ubuntu 10.04
> java version "1.6.0_22"
> Java HotSpot(TM) Client VM (build 17.1-b03, mixed mode, sharing)
>            Reporter: Javier Arias
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> In routes with a split step, when my wrapProcessorInInterceptors method is called, the
 ProcessorDefinition<?> paremeter is referencing the Split definition instead of steps
inside it.
> For example, for the route:
> from("direct:a").routeId("route:a")
>         .split(xpath("//a/b")).id("task:split.products")
>             .log("*** splited ::: body : ${body} ").id("task:handle.that") (*)
>             .setHeader("insplit",constant("in-split")) (*)
>         .end()
>         .log("* aftersplit ::: body : ${body}").id("task:after.split");
> for steps inside the split (*) the ProcessorDefinition is referencing the splitdefinition,
while i think it should point to the log and setHeader steps.
> It can be easily fixed,  in class:::
> org.apache.camel.processor.DefaultChannel
> in the method initChannel, changing
> target = strategy.wrapProcessorInInterceptors(routeContext.getCamelContext(), outputDefinition,
target, next);
> by this:
> target = strategy.wrapProcessorInInterceptors(routeContext.getCamelContext(), traceDef,
target, next);

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

Mime
View raw message