Hi Yes its very clear in the docs at http://camel.apache.org/aggregator2
> Notice that all the completion ways are per correlation key. And you can > combine them in any way you like. It's basically the first which triggers > that wins. So you can use a completion size together with a completion > timeout. Only completionTimeout and completionInterval cannot be used at the > same time. On Fri, May 24, 2013 at 7:20 PM, javamonkey79 <javamonke...@gmail.com> wrote: > I did read the documentation, many times :) > > It was not camel that was wrong - it was my unit test. > > From what I can tell, if you set BOTH a completionSize and a > completionTimeout it will use both: e.g. if you set it to > completionSize="500" completionTimeout="500" for example, it will stop when > it gets too 500 messages or 500ms, whichever comes first. I don't know that > this is clear in the documentation. Can you confirm what I am talking about? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/aggregator-dynamic-completion-size-tp5733048p5733132.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- www.camelone.org: The open source integration conference. Red Hat, Inc. FuseSource is now part of Red Hat Email: cib...@redhat.com Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
