tmi wrote:
>
> Sure, you can specify a batchSize parameter instead of the batchTimeout.
> See http://camel.apache.org/aggregator.html. You can also define your own
> aggregation strategy and completedPredicate as explained in the Camel docs
> and the blog mentioned previously:
> http://tmielke.b
Frank Schwarz wrote:
>
> So, essentially the aggregator waits the specified batchTimeout
> milliseconds, aggregates whatever it finds on the queue and then waits for
> the next round.
>
It aggregates all messages that it has received until the timeout elapses.
The messages are not on any queue
Torsten, thank you for confirming my findings.
So, essentially the aggregator waits the specified batchTimeout
milliseconds, aggregates whatever it finds on the queue and then waits for
the next round.
This is not quite what I was expecting - or to put it differently: Is there
a way to aggregate
On Mon, Apr 20, 2009 at 1:22 PM, tmi wrote:
>
>
> Frank Schwarz wrote:
>>
>> How do you read it?
>> (a) The aggregation is aborted after the batchTimeout, leading to possibly
>> fragmentary messages. The aggregation is started, when the first message
>> is available.
>> (b) The aggregator waits th
Frank Schwarz wrote:
>
> How do you read it?
> (a) The aggregation is aborted after the batchTimeout, leading to possibly
> fragmentary messages. The aggregation is started, when the first message
> is available.
> (b) The aggregator waits the batchTimeout timespan and then begins the
> aggregat
