I am still trying this... nothing seems to work. this is exhausting ! I have tried a few options:
1. Without pax-jms. I had exported broker service from my blueprint and installed the bundle. This way, bundle:capabilities displayed the services exposed. 2. With pax-jms, following https://github.com/apache/karaf/blob/e21fcf86d6160109e54da82d3f6543ed99059985/examples/karaf-jpa-example/karaf-jpa-example-features/src/main/feature/feature.xml#L28, I did almost similar stuff: <capability> osgi.service;objectClass=javax.jms.ConnectionFactory;effective:=active;osgi.jndi.service.name=eai/consumer </capability> Here, bundle:capability <bundle_id> does not list the service. In both cases, I can see the service out there is listed in service:list javax.jms.ConnectionFactory Moreover, I have noticed one thing here: My Bundle A (which depends on JMS) is installed before the bundle B (which provides JMS services). But, I believe this shouldn't have affected this, as bundle was supposed to keep waiting for the JMS service. My few other bundles are dependent on cluster services, and they keep waiting until the cluster services are available. But, this bundle, goes straight away to the failure state. Completely weird. So, in summary: I can install this feature via feature:install (after tweaking the service availability as optional), but not as a bootFeature. I will try to dig a bit more, and post back. Right now, I am totally out of clues :D Regards, Cooshal. -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
