Hi, I would recommend to check the javax.jms import package ;)
Pax JMS uses JMS 2.0 package. If your bundle uses JMS 1.1, even if the ConnectionFactory service is available, as they are not from the same package, it won't work. I fixed similar issue in Decanter JMS last week. Regards JB On 08/05/2019 14:50, cooshal wrote: > Hi: > > although this post is quite old, was there a definite solution to this > problem? > > My problem is similar, such that my bundle requires the osgi service (I got > this while trying to do feature:install ... ) > > osgi.service; effective:=active; > filter:="(&(objectClass=javax.jms.ConnectionFactory)(osgi.jndi.service.name=jms/msg.consumer))"]] > > The "jms/msg.consumer" is already available in the service registry, and > these bundles work properly when I deploy them by dropping in the deploy > folder or install them via bundle:install. > > Additionally, I can see this jms/msg.consumer in the service:list > javax.jms.ConnectionFactory as well. To check, if it is functional, I tried > jms:browse to browse one of the queues. It works fine enough. > > But, I am trying to install this bundle as part of a feature as (provided > that the broker and db services are pre-installed in this custom karaf > distribution): > > <feature name="custom-stats" description="Stats Bundle" version="1.1.1"> > <bundle>file:D:/temp/stats-bundle.jar</bundle> > </feature> > > Regards, > Cooshal. > > > > > > -- > Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
