Thanks Dan! that helped getting rid of the error. It generated other class
not found exceptions but I managed to collect all the jar files that I need.
The error that I'm having now is that it could not find the connection
factory name: javax.naming.NameNotFoundException:
java:activemq/QueueConnectionFactory
I'm thinking that my client doesn't regconize the java: namespace, so I made
the connection factory and the queues global.
Global JNDI namespace
...
activemq
+QueueConnectionFactory
+queue
+----GetForecastRequestQueue
+----GetForecastResponseQueue
...
Then I remove the "java:" in my cxf.xml file So it'll be something like
this:
...
jndiConnectionFactoryName="activemq/QueueConnectionFactory"
jndiDestinationName="activemq/queue/GetForecastRequestQueue"
jndiReplyDestinationName="activemq/queue/GetForecastResponseQueue"
...
Re-deploy the war file and re-execute the client. The client codes still
doesn't seem to like it neither. I don't know what I'm missing or doing
wrong here.
--
View this message in context:
http://cxf.547215.n5.nabble.com/Soap-over-Jms-Error-Insufficient-configuration-for-Conduit-tp5130316p5133296.html
Sent from the cxf-dev mailing list archive at Nabble.com.
