Hi Claus, In the scenario you have specified, it is also possible to call "direct:b" and "seda:b" without involving the the route and/or consumer "direct:a" at all. In this case the current implementation is fine and in fact essential.
There are other possibilities where there may be several other routes (direct:a1, direct:a2) with their own onCompletions flowing into "direct:b" and/or "seda:b". I guess the scoped implementation of onCompletion would then have to correctly chain the onCompletions for the different route chains correctly. Cheers, Ashwin... ----- --------------------------------------------------------- Ashwin Karpe Apache Camel Committer & Sr Principal Consultant FUSESource (a Progress Software Corporation subsidiary) http://fusesource.com http://fusesource.com Blog: http://opensourceknowledge.blogspot.com http://opensourceknowledge.blogspot.com --------------------------------------------------------- -- View this message in context: http://camel.465427.n5.nabble.com/DISCUSS-Route-scoped-onCompletion-tp3344202p3367031.html Sent from the Camel Development mailing list archive at Nabble.com.
