Thanks Christian.
I did this:
packages:exports | grep javax.jms, and I get:
karaf@root> packages:exports | grep javax.jms
96 javax.jms; version="1.1.0"
Looks like I have only one. Also, even if there were multiple bundles
exporting the javax.jms, I thought the whole point is that OSGi would only
wire up ONE of them to my bundle that requires it, and then just use that?
My bundle is marked ACTIVE:
[ 64] [Active ] [ ] [ 60] OSGi-Enabled MSP Load Balancer
(1.0.0.SNAPSHOT)
so presumably, it has been resolved to one of the particular instances (if
there were multiples of the package exporters).
If I just look for JMS:
karaf@root> packages:exports | grep jms
96 javax.jms; version="1.1.0"
97 org.springframework.jms; version="3.0.6.RELEASE"
97 org.springframework.jms.config; version="3.0.6.RELEASE"
97 org.springframework.jms.connection; version="3.0.6.RELEASE"
97 org.springframework.jms.core; version="3.0.6.RELEASE"
97 org.springframework.jms.core.support; version="3.0.6.RELEASE"
97 org.springframework.jms.listener; version="3.0.6.RELEASE"
97 org.springframework.jms.listener.adapter; version="3.0.6.RELEASE"
97 org.springframework.jms.listener.endpoint; version="3.0.6.RELEASE"
97 org.springframework.jms.remoting; version="3.0.6.RELEASE"
97 org.springframework.jms.support; version="3.0.6.RELEASE"
97 org.springframework.jms.support.converter; version="3.0.6.RELEASE"
97 org.springframework.jms.support.destination; version="3.0.6.RELEASE"
Could the springframework.jms be the "other" package? Since I can't get rid
of springframework (required for some of our services bundles), how do I
resolve this? Should I explicitly import the springframework version? OR
just specify version to import as 3.0.6.RELEASE ??
--
View this message in context:
http://karaf.922171.n3.nabble.com/JMS-messaging-issue-tp3882408p3884119.html
Sent from the Karaf - User mailing list archive at Nabble.com.
