The original exchange will only complete after all the splitter work, so when that is done you know its done.
Also each splitted exchange has exchange properties that indiciate if the split is done or not, you could use as alternative to know if the splitter is done. On Thu, Oct 1, 2015 at 8:56 AM, dermoritz <tantea...@hotmail.com> wrote: > My camel route is configured like this (pseudocode) > > from(direct:in).to(jdbc:db).split().body().streaming().parallelProcessing() > .process(doSomething).process(createDBquery).out(jdbc:db) > > The jdbc endpoint is configured to put out JdbcOutputType.StreamList. The > route is triggered by sending a select query into direct:in. Each line from > db is handled in doSomething. It creates a special result object that is > converted into a query to write the result into db. > > My main problem is how to detect if the complete result from db was handled- > I want to know when it is finished. > > I tried to use an EventNotifier and filtered on ExchangeCompletedEvent. But > this event seems to be raised for every result written into db. Now i am > considering the use of RoutePolicy / overriding "onExchangeDone" but would > this change anything? > > What are the exact semantics of both especially for routes that create new > exchanges (e.g. by split) on their way? Is their a clean way to detect when > my route is finished? > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Camel-ExchangeCompletedEvent-vs-RoutePolicy-onExchangeDone-tp5772140.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2nd edition: https://www.manning.com/books/camel-in-action-second-edition
