On Fri, Jun 24, 2011 at 5:24 PM, Guillaume Nodet <gno...@gmail.com> wrote: > It seems there's currently no easy way to add an InterceptStrategy > without having full control over the CamelContext. I think what would > be needed is a static global list of InterceptStrategy that would be > automatically added to each CamelContext at creation time. That > should be an easy and safe enhancement to the DefaultCamelContext, but > I need to make sure it fulfills the need before going that way. >
If you use Spring XML files with Camel then you can define X number of spring beans as interceptors, and they will be picked up and use by <camelContext>. There is a list of supports types here: http://camel.apache.org/advanced-configuration-of-camelcontext-using-spring.html That said we may want to make that likewise easier to work with OSGi as well. And some way of defining filters/patterns to include/exclude, as the OSGi service registry can contain a JVM wide list of interceptors. And you may only want a certain number of interceptors. > Actually, I'm investigating the exact same thing to include in > ServiceMix. If you're interested, monitor the servicemix dev list as > I plan to start a thread about that next week. > > On Fri, Jun 24, 2011 at 17:10, Marco Westermann <marwesterm...@gmx.de> wrote: >> Hi, >> >> is it somehow possible to intercept a route from outside the camel context? >> I'd like to write a module which intercept every route which is deployed in >> SMX and does something with the intercepted messages. >> >> >> Thank you in advance. >> >> Marco >> > > > > -- > ------------------------ > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ > ------------------------ > Open Source SOA > http://fusesource.com > -- Claus Ibsen ----------------- FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
