This content has been marked as final. Show 2 replies
Why not use our client stack instead of the jwsdp, just because you use wscompile does not mean you need to use the sun ws stack.
But I have fixed this issue after removing jbossall-client.jar from client classpath. it works fine.
I have the same exception while developing web based client using JWSDP 2.0.
Could you please explain how to remove jbossall-client.jar from the client classpath?
Do you mean build classpath or run-time (execution) classpath?
I am developing using Eclipse with JbossIDE and can't find the jbossall-client.jar in build classpath.
Besides, I don't understand how to remove a jar from run time classpath which, to my mind, is supplied by Jboss by default.
Thanks in advance,