On Wed, Oct 19, 2011 at 10:38 AM, Michael Dewitte <[email protected]> wrote: > Hi, > > I'm using SMX 4.3 with Camel 2.6 > > I'm trying to have automatic processing done when we receive any message in > any route. The purpose is to have a single correlationId to track the > incoming message if it undergoes several routes that can even be in several > camelcontext (those routes can be deployed in different bundles). > I already did it using the interceptFrom in the definition of all my > camelContext. But I'd like to have it defined outside of the camelcontext > definition, since > - I want to have it defined for all the camelcontext (so I want to be sure > not to forget it) > - many people will write routes and camelcontext bundles, and I don't want > to force them to put this in their config, since they can forget and it will > add extra "noise" to their definitions > > Is there a way to do this ? I already tried to see if I could configure > another camelcontext than the DefaultCamelContext, (that could be a > solution), but haven't found how to do it. I assume there is also some > possibility at the level of OSGI, but haven't found a clue about it... > > Any help would be greatly appreciated, >
This is something that we are looking into the future with both SMX and Camel. To have it easily be able to hot-deploy interceptors, tracers, and whatnot into SMX, and have those influence Camel apps. Its on the roadmap, in that a bit cryptical title - "More flexible routes at runtime" http://camel.apache.org/camel-30-roadmap.html > Mike > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
