[
https://issues.apache.org/jira/browse/CAMEL-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448551#comment-13448551
]
Claus Ibsen commented on CAMEL-5567:
------------------------------------
Also we have a ticket reported by Christian S. about supporting nested
expressions, as his use-case was to use nested expressions as parameter
bindings to a method call expressions. This ticket is AFAIR currently scheduled
for Camel 3.0.
Something a like:
{code:xml}
<method ref="myBean" method="myMethod">
<compoundExpression>
<header>foo</header>
<xpath>/foo/bla</xpath>
<constant>true</constant>
</compundExpression>
</method>
{code}
So there is some synergy to this one. But we have to be careful adding this to
the DSL to avoid bloat.
Also the DSL in Camel 2.x should be kept stable etc.
> Add Multiple correlation Ids to the Aggregator component
> --------------------------------------------------------
>
> Key: CAMEL-5567
> URL: https://issues.apache.org/jira/browse/CAMEL-5567
> Project: Camel
> Issue Type: Improvement
> Reporter: Alan Foster
>
> 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="http://camel.apache.org/schema/spring";>
> <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: http://www.atlassian.com/software/jira
