If you're using blueprint the CamelContext is already automatically registered in the OSGi Service Registry. Just type 'ls' in Karaf and you'll notice there's a CamelContext service associated with each bundle. So yes, you can just lookup the CamelContext of another bundle and start/stop a particular route.
On Fri, Dec 13, 2013 at 5:51 PM, Hilderich <hilde.sch...@yahoo.de> wrote: > Dear Camel Support Team, > > We have about 3 bundles running in an OSGi-Container (Karaf) and each has > its own > CamelContext - we are using Aries Blueprint by the way. > Now we have the requirement to stop a route from another CamelContext. > Furthermore this CamelContext is defined in another bundle. Can I take > access to > this CamelContext and stop the route? > > Can this be done and what is here the best practice? I was thinking about a > OSGi-Service. > > Many thanks and kind regards > Hilderich > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Access-another-CamelContext-tp5744744.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
