Can anyone tell me how this was actually resolved? Was it a problem with the
jar that was delivered with JBoss, or a problem with the version that was
deployed with the application?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4179414#4179414
Reply to the
I had this same error and found that it was because I was including some JAX
RPC libs in my EAR file that did not mesh well with the libs on the JBoss
server install.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4167193#4167193
Reply to the post :
Has anyone solved this problem?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4065907#4065907
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4065907
___
jboss-user mailing list
Did anyone find a solution to this problem. Recently upgraded from 4.0.5 to
4.2.1, having the same problem.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4065466#4065466
Reply to the post :
I found a solution... I had to add a few jars to the WSTOOLS classpath in
wstools.bat, but it was different for JRE 1.5 vs 1.6.
Using JRE 1.5.x I had to add the following:
set WSTOOLS_CLASSPATH=%WSTOOLS_CLASSPATH%;%JBOSS_HOME%/client/wsdl4j.jar
| set
