Thanks for the update. This might help other users.
On Fri, Jan 3, 2014 at 10:58 AM, Hilderich wrote:
> Hello *,
>
> I figured it out:
>
> In Apache Karaf I checked the service metadata via:
>
>
>
> The following output gave me a view to the server metadata
> and I saw the key *camel.context.na
Hello *,
I figured it out:
In Apache Karaf I checked the service metadata via:
The following output gave me a view to the server metadata
and I saw the key *camel.context.name*
In my blueprint I was able to write the following:
The crucial thing above is the filter attribute.
That's it.
Hello again,
My approach above doesn't work steadily because more than one bundle exports
a service
with the same interface org.apache.camel.CamelContext. Now I have the
situation that
sometimes the Camel-Context is from that and then later the Camel-Context
is from the other bundle.
How can I use
Many thanks!
--
View this message in context:
http://camel.465427.n5.nabble.com/Access-another-CamelContext-tp5744744p5744847.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Yeah or use JMX to stop the route on the other bundle.
On Sun, Dec 15, 2013 at 12:33 PM, Richard Kettelerij
wrote:
> 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
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
particul
