No, the problem is not that WebSphere doesn't see the javax.jms.*
classes. It's just the opposite: they are in the classpath of both the
server classloader and the application classloader. In parent first
mode that's not an issue, but in parent last mode the result is that
at runtime the relationsh
Hello
I'm atm writing a Software to connect to each accessible Soap-WS.
But i have many problems by creating Calls for any Objects.
My project is written in Java and i'm using your wsimport and your Libraries.
Primitive objects aren't a problem, only Objects.
My way is :
- getting wsdl
- creatin
Thanks Andreas,
I tried removing jms.jar from the war and then deployed with "parent last"
on WAS.
WAS now fills the logs with huge exceptions now :
[10/25/08 20:57:34:171 EDT] 0022 ConnectionFac E J2CA0009E: An
exception occurred while trying to instantiate the ManagedConnectionFacto
as andreas mentioned we need to determine which CL *server classloader or
application classloader is loading the class
assuming you're using Spring ConnectionFactories..can we see your
jmsContext.xml it should look something like:
This sounds lik
Hi mgainty,
Actually that is my jmsContext.xml. I also trying my luck
on JSF forum
( http://forums.sun.com/thread.jspa?threadID=5342580)
and spring forum
( http://forum.springframework.org/showthread.php?p=209833#post209833)
And so far Nabble has been the only helpful forum, thanks to peopl
