The splitted exchanges have a correlation id that points to its
parent, so you can essential know which exchange is which as the
parent will not have a correlation id.
This is set on the splitted exchanges
copy.setProperty(Exchange.CORRELATION_ID, id);
And yeah a route policy with the onExchangeDone should call when you
are done, and only for the original exchange as its for routes only
On Thu, Oct 1, 2015 at 9:27 AM, dermoritz <tantea...@hotmail.com> wrote:
> Thanks for your quick reply Claus,
>
> my problem is that from inside ExchangeCompletedEvent or onExchangeDone i
> don't know if it is the original exchange or a split exchange. Or: How to
> know if an exchange is the "original exchange"?
> (i know how to detect if a splitter is done, but in my case i only want to
> know about "original message")
>
> To come back to this threads title: Are there semantic differences between
> ExchangeCompletedEvent and RoutePolicy.onExchangeDone?
>
> In meantime i also looked into Camel in Action (a very nice book) and i read
> about "onCompletion" synchronization callbacks i am not sure if those are
> better options for my use case:
>
> camel is called inside another infrastructure (java app that do many other
> things) and i want camel to call back to this infrastructure if the
> "original message" is done.
>
>
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-ExchangeCompletedEvent-vs-RoutePolicy-onExchangeDone-tp5772140p5772142.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
