Re: Processing Asynchronous Interceptors

Thanks for the reply Claus. That explains the behavior I have been seeing Essentially, I was expecting wrongly of asyncprocessors to kick off a separate thread and continue processing the exchange. Thanks, Brian -- View this message in context:

Re: Processing Asynchronous Interceptors

Hi, Still awaiting any suggestions/information on the question. At the moment working around the problem by customizing processor handling in already initiated threads. Regards, Brian -- View this message in context:

Re: Processing Asynchronous Interceptors

My apologies, moved the topic to the users forum -- View this message in context: http://camel.465427.n5.nabble.com/Processing-Asynchronous-Interceptors-tp5738810p5738851.html Sent from the Camel - Users mailing list archive at Nabble.com.

Enable/disable Intercept strategy at runtime

HI, I am looking for a way to add interceptstrategy to a camel context during runtime after the camel context has started. Similarly,I would also want to disable the respective interceptstrategy while the camel context continues to run. 1. Can this be done ? If yes how do I go about it? I have

Re: Enable/disable Intercept strategy at runtime

Thanks Claus, With the current version though, is it achievable only through camelcontext restarts? Thanks, Brian -- View this message in context: http://camel.465427.n5.nabble.com/Enable-disable-Intercept-strategy-at-runtime-tp5737154p5737160.html Sent from the Camel - Users mailing list

Re: Enable/disable Intercept strategy at runtime

Thanks Claus that was helpful. Beats having to restart the context. -- View this message in context: http://camel.465427.n5.nabble.com/Enable-disable-Intercept-strategy-at-runtime-tp5737154p5737178.html Sent from the Camel - Users mailing list archive at Nabble.com.