Hi Claus, I have read this page already and basically it's what I am doing at the moment. The reason I use a handcrafted version of a context-wide interceptor is that the project is using Java EE 7 without any Spring involved, so I cannot use most of the Camel features that depend on Spring's functionality.
As I said, my solution works but I would rather have the InterceptStrategy being attached to only those processors that I actually want to wrap instead of all processors and having to decide on a case-by-case basis whether to pass the call through or to do some custom around-voodoo. Just for clarification: is it correct behavior that ToDefinition's intercept strategies do not work (or at least not in my case)? Thanks again, Sven -- View this message in context: http://camel.465427.n5.nabble.com/InterceptStrategy-added-to-ToDefinition-is-not-executed-tp5754794p5754823.html Sent from the Camel - Users mailing list archive at Nabble.com.
