On Tue, Jul 27, 2010 at 5:43 PM, Marco Crivellaro
<mcr...@optasportsdata.com> wrote:
>
> Hi all,
> we have a route which is delivering of a given message to a list of
> endpoints (HTTP, MAIL, FTP...)
> to achieve this we are using a recipentList (the endpoint list is dinamic).
> In order to process all deliveries in parallel we are using
> parallelProcessing
>
> once the delivery to a given endpoint is processed we need to update a
> delivery trail through a web service, to achieve this we have introduced an
> aggregationStrategy
>
> so far so good... this is the route (simplified):
>
> from("direct:start")
> .recipientList(header("recipientListHeader").tokenize(","))
> .parallelProcessing().executorService(customThreadPoolExecutor)
> .aggregationStrategy(new
> RecipientAggregationStrategy()).to("direct:completed")
>
>
> the issue we have is that the exchanges starts to hit the
> aggregationStrategy once all of them have been processed so if one of them
> takes a long time we cannot update our delivery information trail and
> therefore we do not know if they've been already updated.
> is there a way to process the exchanges at aggregationStrategy as soon as
> they reach the endpoint?
>
No
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/recipientList-parallelProcessing-aggregationStrategy-tp2255971p2255971.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
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
