On Mon, Feb 28, 2011 at 10:01 AM, Ekatus Atimoss <[email protected]> wrote: > Hi again, > > looks like it's not that easy with unzipping everything from the WMQ rar > into lib\ext - looks like I'm in classloader hell now. I've tried different > combinations: when putting everything under lib\ext, the log complained > about javax/jms/QueueConnectionFactory not being found, when adding jms.jar > to lib\ext, the complaint was "ConversionNotSupportedException: Failed to > convert property value of type 'com.ibm.mq.jms.MQQueueConnectionFactory' to > required type" - even when stuffing the WMQ jarsinto an OSGi bundle using > Eclipse...no such luck. > > If necessary, I could post the stack traces. > > Could it be that using SM 4 together with a recent WMQ is a rather exotic > use case? I'm working in the German financial industry where WMQ is a > de-facto standard. >
As a sidenote: I have seen people on the Camel mailing list deploying WMQ and Camel in SMX 4 and having it working. I think IBM provides OSGI jars of their JMS client. > kind regards > Michael > > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/ServiceMix-4-deploy-JCA-rar-tp3400074p3402960.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
