You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Hadrian Zbarcea (JIRA)" <ji...@apache.org> on 2008/10/08 07:53:53 UTC
[jira] Updated: (CAMEL-393) BatchProcessor always consumes directly
from endpoint ignoring previous steps
[ https://issues.apache.org/activemq/browse/CAMEL-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hadrian Zbarcea updated CAMEL-393:
----------------------------------
Fix Version/s: 2.0.0
(was: 1.5.0)
> BatchProcessor always consumes directly from endpoint ignoring previous steps
> -----------------------------------------------------------------------------
>
> Key: CAMEL-393
> URL: https://issues.apache.org/activemq/browse/CAMEL-393
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Reporter: Roman Kalukiewicz
> Assignee: Hadrian Zbarcea
> Fix For: 2.0.0
>
>
> 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 {{setHeader()}}.
> 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.