Register a Camel POJO endpoint for other OSGi bundles

[michael.wengle]

I would like to have a route in one OSGi bundle and this route is accessing an endpoint that is provided by another bundle. 'ServiceMix Bean' is doing exactly this for JBI endpoints. Is it possible to do this for non JBI endpoints (without losing the Camel Headers)?

Some details to my question:

The route could look like this: from("activemq:qwer").to("A").to("B").to("C");

The endpoint on the other bundle is B;

The order is important and every endpoint needs the current message that has been changed from the endpoint beforehand.

What I don't want is something like this:

Bundle 1: from("activemq:qwer").to("A").to("vm:preB");

Bundle 2: from("vm:preB").to("B").to("preC");

Bundle 1: from("vm:preC").to("C");

One workaround I already know is this:

<osgi:reference id="delayService" interface="org.apache.camel.Processor" filter="(processorId=delay)" />

from("activemq:qwer").to("delayService");

but I hope there is a neat solution to my problem without accessing OSGi services.

[davsclaus]

The bean component should lookup in OSGi service registry first. So you may be able to do "bean:A"

[njiang]

I'm afraid you have to do this,  as the you can't access other bundles bean from the camel context without export it as OSGi service.

[michael.wengle]

Thanks for the answer. I know now at least, that I'm not missing a simpler way to do it.