You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Alan Foster (JIRA)" <ji...@apache.org> on 2012/09/04 20:43:12 UTC

[jira] [Updated] (CAMEL-5567) Add Multiple correlation Ids to the Aggregator component

     [ https://issues.apache.org/jira/browse/CAMEL-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alan Foster updated CAMEL-5567:
-------------------------------

    Description: 
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

  was:
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()</simple>
            </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

    
> 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