Hi Yeah its a little bug. I have reproduced the problem and working on a fix. https://issues.apache.org/jira/browse/CAMEL-7111
On Mon, Jan 6, 2014 at 12:13 PM, Minh Tran <[email protected]> wrote: > I am using 2.12.2. > > On 06/01/2014, at 6:42 PM, Claus Ibsen <[email protected]> wrote: > >> What version of Camel do you use? >> >> On Mon, Jan 6, 2014 at 12:03 AM, Minh Tran <[email protected]> wrote: >>> Hi all >>> >>> I'm currently using multicast in my route with an aggregation strategy and >>> I'm finding that if my multicast only has one route defined in it, then my >>> aggregation strategy is never called. Is this expected behaviour? I would >>> have expected the first call to the aggregation strategy to occur with the >>> newExchange being null. >>> >>> eg >>> … multicast(myStrategy).to("direct:foo", "direct:bar").end() >>> myStrategy is called, however >>> >>> … multicast(myStrategy).to("direct:foo").end() >>> myStrategy is never called >>> >>> Admittedly there's no point having a multicast if it only goes to one route >>> but I am putting this in place because I am expecting to add extra routes >>> in the future to the multicast. >>> >>> Thanks >>> >> >> >> >> -- >> Claus Ibsen >> ----------------- >> Red Hat, Inc. >> Email: [email protected] >> Twitter: davsclaus >> Blog: http://davsclaus.com >> Author of Camel in Action: http://www.manning.com/ibsen >> Make your Camel applications look hawt, try: http://hawt.io > -- Claus Ibsen ----------------- Red Hat, Inc. Email: [email protected] Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
