I got this working now =)
The correct namespace for ActiveMQWASInitialContextFactory is actually
org.apache.activemq.jndi.ActiveMQWASInitialContextFactory. Note the "WAS"
there is in the middle. I experienced JNDI lookup failures too, and the key
thing to overcome those was to define the redun
I have also found that there exists a bug in WAS 6.1.0 (< 6.1.0.13) for
creating queues or topics for an external JMS provider. The IBM page related
to this (and the fix) is
http://www-01.ibm.com/support/docview.wss?uid=swg1PK48167 here .
--
View this message in context:
http://www.nabble.com/A
I have not gotten much further than you have, but I have noticed that for
ActiveMQ 5.2, the the name of the class is
org.apache.activemq.jndi.ActiveMQWASInitialContextFactory, not
org.activemq.jndi.ActiveMQWASInitialContextFactory.
--
View this message in context:
http://www.nabble.com/ActiveMQ
Whilst I thought that all the earlier steps had gone well, I have since
restarted my WAS and I am getting a class not found error for the
initialcontextfactory - which seems strange, I have taken all the .jar files
from my activeMQ install/lib and have out them in the WAS classpath
(WAS_INSTALL_RO
