Thanks for the tip Ashwin! In the meantime I was able to isolate the usecase from the given environment to be able to use a current camel release. The aggregator2 component fulfills my needs since I can combine "completionSize", "completionInterval" as well as "forceCompletionOnStop" as triggers to complete an aggregation interval. The transaction problems of the old aggregator are also solved by using the persistence adapter of aggregator2.
I am now trying to solve my case with aggregator2. Cheers Stefan On Fri, Mar 30, 2012 at 15:00, Ashwin Karpe <aka...@fusesource.com> wrote: > Hi, > > Have you looked into Scheduled Route Policies in Camel. These or the quartz > component should allow you to perform periodic activity using camel > routes... > > http://camel.apache.org/scheduledroutepolicy.html > http://camel.apache.org/scheduledroutepolicy.html > http://camel.apache.org/simplescheduledroutepolicy.html > http://camel.apache.org/simplescheduledroutepolicy.html > http://camel.apache.org/cronscheduledroutepolicy.html > http://camel.apache.org/cronscheduledroutepolicy.html > > Cheers, > > Ashwin... > > ----- > --------------------------------------------------------- > Ashwin Karpe > Apache Camel Committer & Sr Principal Consultant > FUSESource (a Progress Software Corporation subsidiary) > http://fusesource.com > > Blog: http://opensourceknowledge.blogspot.com > --------------------------------------------------------- > -- > View this message in context: > http://camel.465427.n5.nabble.com/Best-way-to-implement-this-usecase-tp5603631p5606587.html > Sent from the Camel - Users mailing list archive at Nabble.com.
