Custom Aggregator

[Leen Toelen <to...@gmail.com>]

Hi,

I am in need for a customized Aggregator. Some specific needs are
- one type of (jms) message starts the aggregation
- this message is used to define the logic on what other messages to
correlate. The logic is very dynamic, and might even involve database
lookups
- each aggregation change/event might change the completion strategy
and/or timeout
- the timeout is defined by the aggregated exchanges and changes dynamically
- an exchange might be aggregated by multiple aggregators
- aggregation should be persistent

is it possible to customize the behaviour of the aggregator this much?

Regards,
Leen

Re: Custom Aggregator

[Claus Ibsen <cl...@gmail.com>]

You can provide the completion conditions as headers, so that means
you can customize this dynamic.
The aggregator has pluggable API for persistent store, so you can
develop you own. Or use camel-hawtdb.

On Wed, Oct 13, 2010 at 11:10 PM, Leen Toelen <to...@gmail.com> wrote:
> Hi,
>
> I am in need for a customized Aggregator. Some specific needs are
> - one type of (jms) message starts the aggregation
> - this message is used to define the logic on what other messages to
> correlate. The logic is very dynamic, and might even involve database
> lookups
> - each aggregation change/event might change the completion strategy
> and/or timeout
> - the timeout is defined by the aggregated exchanges and changes dynamically
> - an exchange might be aggregated by multiple aggregators
> - aggregation should be persistent
>
> is it possible to customize the behaviour of the aggregator this much?
>
> Regards,
> Leen
>



-- 
Claus Ibsen
Apache Camel Committer

Author of Camel in Action: http://www.manning.com/ibsen/
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus