Fwiw, I've just fixed CXF-7078 which should allow the cxf jms transport to use the JMS 2.0 api. I think the best solution would be to have a JMS API bundle that exports the javax.jms package in versions 1.1 and 2.0 at the same time. Something along the following bundle:
wrap:mvn:org.apache.geronimo.specs/geronimo-jms_2.0_spec/1.0-alpha-2$overwrite=merge&Export-Package=javax.jms;uses:=javax.transaction.xa;version=1.1,javax.jms;uses:=javax.transaction.xa;version=2.0 I think maybe the geronimo spec jar could export both versions directly. This may be sufficient to fix all problems, if the various features reference the jms api with the dependency="true" flag to allow our fixed bundle to be used instead. 2016-10-07 9:57 GMT+02:00 Benjamin Graf <benjamin.g...@gmx.net>: > Hi, > > Actually it is hard getting messaging systems working with Karaf if they > are using different version of the jms API (1.1 vs 2.0) like ActiveMQ > Artemis or IBM WebsphereMQ > 8. Therefor I would suggest to add a > jms-spec feature for either 1.1 version and 2.0 version. This allows to > add it for example to the corresponding spring-jms features (3.x -> JMS > 1.1, 4.x -> JMS 2.0) If you need a specific JMS version to get resolved > you can using override feature or explicitly declare it in > org.apache.karaf.features.cfg. > > What do you think? Better suggestions? > > Regards, > > Benjamin > > > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: gno...@redhat.com Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
