Update to the JMS 2.0 API

It is presently impossible to use Fuse or ActiveMQ to integrate with IBM WebSphere MQ (W-MQ) 8.0. This is exactly the sort of integration that software like Camel on Fuse should be good at but, unfortunately, it is prevented by the lack of JMS 2.0 support.

W-MQ 8.0 is based on JMS 2.0. Previous W-MQ drivers (7.5.x) used JMS 1.1 and, although it could be fiddly, integration between Fuse/A-MQ and W-MQ 7.5.x was possible. IBM is no longer supplying 7.5.x drivers to 8.0 customers, and it is not clear whether they would work even if they were available.

IBM does release the JMS 2.0 classes in a pre-requisites bundles (and they exist in Geronimo JMS 2.0 as well). However, the ActiveMQ bundles are specified to wire only to javax.jms version 1.1. camel-jms will use later versions of JMS, but installing both 1.1 and 2.0 JMS bundles causes classloading conflicts, and puts the Fuse/ActiveMQ container into an untested, unsupportable configuration.

To fix this problem ActiveMQ bundles need to be capable of wiring to a JMS API bundle that provides javax.jms version 2.0 at later, as well as 2.1. This would allow the 1.1 bundle currently shipped to be replaced by a 2.0 bundle, either from IBM or from Geronimo.This configuration will also need to be tested.