Thanks Kyle-
Thanks for the info but I believe the problem still exists:
I need to define the QManager etc in WebLogic at startup in order to bind them into WL�s JNDI. The way I do this is to instantiate the QueueConncectionFactory and Queue and then bind them. Unfortunately I see no way to do this without using the com.ibm classes. In the
doc you provided it says (p 201):
If a JNDI namespace is not available, it is possible to create factory objects at runtime. However, using this method reduces the portability of the JMS application because it requires references to WebSphere MQ specific classes. The following code creates a QueueConnectionFactory with all default settings:
factory = new com.ibm.mq.jms.MQQueueConnectionFactory();
So it looks like I have to write an adapter after all. I�m curious, though, how WAS is able to bind MQJMS into JNDI as javax.jms objects.