Hi Krzysztof, yes: geronimo-jms_1.1_spec exports javax.jms with version 1.1 but imports the package with [1.1,] (right open). As a result the javax.jms export from jms-api bundle are pulled in. This leads to camel-jms, spring-jms, activemq, camel-activemq failing on restart of container.
Maybe JB can provide some help. Initially I would like confirmation that the Import-Package version range is incorrect. Thanks and Regards, Michael 2016-03-21 12:20 GMT+01:00 Sobkowiak Krzysztof <[email protected]>: > Hi > > I think it was my mistake. I thought it was the problem that Spring forces > installation of geronimo_[jms,jta]_1.1_spec. So probably you have another > problem. > > Regards > Krzysztof > > On 21.03.2016 11:38, Michael Täschner wrote: > > Hi Krzysztof, > > > > thanks for your response, how does this jta issue relate to jms ? If it > > applies, I guess I'll get to use it with ServiceMix 7 and onwards right?! > > > > Thanks and Regards, > > Michael > > > > 2016-03-21 11:34 GMT+01:00 Sobkowiak Krzysztof < > [email protected]>: > > > >> Hi Michael > >> > >> I think you have the problem solved here > >> https://issues.apache.org/jira/browse/KARAF-4358. The fix will be > >> available with Karaf 4.0.5. > >> > >> Regards > >> Krzysztof > >> > >> > >> > >> > >> On 21.03.2016 11:22, Michael Täschner wrote: > >>> Hi, > >>> > >>> noone having issues with deploying jms-api 2.0 in ServiceMix/Karaf ? > The > >>> "right-open" import of "javax.jms" in geronimo-jms_1.1_spec is really > >>> bugging me especially since it is always a dependency for camel-jms, > >>> activemq, etc. Any suggestions? > >>> > >>> Thanks and Best Regards, > >>> Michael > >>> > >>> 2016-03-17 9:06 GMT+01:00 Michael Täschner <[email protected]>: > >>> > >>>> Hi Servicemix Users, > >>>> > >>>> triggered by a providers update of tibco JMS we're looking into > getting > >>>> JMS 2.0 running in the container. Currently camel-jms, spring-jms and > >>>> activemq (plus camel-activemq) all run on JMS 1.1 api provided > >>>> by org.apache.geronimo.specs/geronimo-jms_1.1_spec/1.1.1 (I will come > >> back > >>>> to this). Looking at Camel there will be JMS 2.0 support with > >> camel-sjms ( > >>>> https://issues.apache.org/jira/browse/CAMEL-9508) but feature still > >>>> requires JMS 1.1 api. > >>>> > >>>> We have a custom in-house camel jms component based on previous > >> ServiceMix > >>>> 3.4 binding component and I looked into upgrading it to use JMS 2.0. I > >>>> started by deploying javax.jms/javax.jms-api/2.0.1 and this leads to > >> major > >>>> issues in the container. The initial resolution is fine but upon > >> container > >>>> restart, all ServiceMix provided ActiveMQ and Camel-JMS related > bundles > >> go > >>>> into "INSTALLED" state. This left me puzzled until I saw that > >> geronimo-jms > >>>> spec declares Import-Package javax.jms;version="1.1" which is > >> interpreted > >>>> as right-open range (version="[1.1,]"). As a result it imports and > >>>> re-exports javax.jms version 2.0 provided by the separate API bundle. > I > >>>> think this breaks modularity and prevents me from running multiple jms > >> apis > >>>> and providers. Is this intended or a bug of the geronimo jms bundle > >>>> configuration? > >>>> > >>>> Thanks and Best Regards, > >>>> Michael > >>>> > > -- > Krzysztof Sobkowiak > > JEE & OSS Architect, Integration Architect > Apache Software Foundation Member (http://apache.org/) > Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/) > Senior Solution Architect @ Capgemini SSC ( > http://www.capgeminisoftware.pl/) >
