You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2008/01/13 13:31:46 UTC

[jira] Resolved: (CAMEL-288) support to set the aggregation stragey of multicastProcessor

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

Willem Jiang resolved CAMEL-288.
--------------------------------

    Resolution: Fixed

The patch is in the svn repository now.

> support to set the aggregation stragey of multicastProcessor
> ------------------------------------------------------------
>
>                 Key: CAMEL-288
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-288
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.2.0
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 1.3.0
>
>
> I have a use case , the router configuration could like this
>                from("direct:a").multicast().to("direct:x", "direct:y", "direct:z");              
>                from("direct:x").process(new AppendingProcessor("x")).to("direct:aggregater");
>                from("direct:y").process(new AppendingProcessor("y")).to("direct:aggregater");
>                from("direct:z").process(new AppendingProcessor("z")).to("direct:aggregater");
>                              from("direct:aggregater").aggregator(header("cheese"), new BodyAggregatingStrategy()).
>                         completedPredicate(header("aggregated").isEqualTo(3)).to("mock:result");
> Now I send the message to endpoint "direct:a" and I want to get the final result of the processors.
> And this requirement  is much like the CAMEL-260.

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