camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Müller (JIRA) <>
Subject [jira] [Commented] (CAMEL-5567) Add Multiple correlation Ids to the Aggregator component
Date Sun, 26 May 2013 21:31:20 GMT


Christian Müller commented on CAMEL-5567:

I'm also not convinced of this. By adding one line in the route, you can accomplish the same:
<setHeader headerName="myKey"><header>foo</header></setHeader>

<setHeader headerName="myKey"><xpath>/foo/bla</xpath></setHeader>

<setHeader headerName="myKey"><constant>true</constant></setHeader>

Let's keep the DSL as simple as possible...
> Add Multiple correlation Ids to the Aggregator component
> --------------------------------------------------------
>                 Key: CAMEL-5567
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Alan Foster
>             Fix For: 3.0.0, Future
> Currently the aggregator component allows users to specifiy one expression that they
would like to use for aggregation
> It would be nice to add many different correlation expressions for all of the different
payload contents that an aggregator can receive
> For instance it may look like 
> {code}
> <camelContext xmlns="">
>     <route>
>         <from uri="direct:start"/>
>         <aggregate strategyRef="aggregatorStrategy" completionTimeout="3000">
>             <correlationExpression>
>                 <!-- If this xpath returns nothing try the next expression etc -->
>                 <xpath>/AcmeServiceResponse/CorrelationId/text()</xpath>
>                 <xpath>/FooResponse/Id/text()</xpath>
>                 <xpath>/CorrelationKey/text()</xpath>
>             </correlationExpression>
>             <to uri="mock:aggregated"/>
>         </aggregate>
>     </route>
> </camelContext>
> {code}
> I wonder what your thoughts are on this suggestion? If it seems like a good idea I can
start to make a patch for it
> Alan

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message