camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] Resolved: (CAMEL-393) BatchProcessor always consumes directly from endpoint ignoring previous steps
Date Tue, 30 Dec 2008 10:26:05 GMT


Claus Ibsen resolved CAMEL-393.

       Resolution: Fixed
    Fix Version/s: 1.5.1

This is fixed by Martin's patch

> BatchProcessor always consumes directly from endpoint ignoring previous steps
> -----------------------------------------------------------------------------
>                 Key: CAMEL-393
>                 URL:
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: Roman Kalukiewicz
>            Assignee: Hadrian Zbarcea
>             Fix For: 1.5.1, 2.0.0
>         Attachments: CAMEL_393.patch
> Aggregator when created connects itself directly to the endpoint it 'originates' - not
to the last step of processing so in such case
> {code}
> from("seda:header").setHeader("visited", constant(true)).aggregator(header("cheese")).to("mock:result");
> {code}
> at {{mock:result}} _visited_ header is not set and in fact there are two different routes
created that start from {{seda:header}}: one directly to aggregator, and the second one to
> In case of direct endpoint everything works because direct component invokes flows one-by-one
so it will set the header, and then aggregate, but with seda it doesn't work.
> Lets look at the test I added to {{AggregatorTest}} class to see the problem ({{_testAggregatorNotAtStart()}}).
This test doesn't pass so far and I was unable to fix it, because I'm not good enough in DSL
code. maybe someone could handle this.
> Another solution is to let to specify aggregator in RouteType so it could be used only
just after {{from()}}.

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

View raw message