I had the same issue you were having.
Whats happening is that the class SOAPMessage is beign loaded by the rt.jar in the JDK_HOME/jre/lib folder.
You just have to point to the jbossws-native-saaj.jar in the JBOSS_HOME/lib/endorsed folder to get rid of this message.
If you use an option of -verbose:class you will see the rt.jar being used for class SOAPMessage.
so I used these options
-Dsun.lang.ClassLoader.allowArraySyntax=true
-Djava.endorsed.dirs=C:\AFSF\jboss5.1.0.GA\lib\endorsed
These dont help by themselves so I used:
-Xbootclasspath/p:${JBOSS.endorsed}\jbossws-native-saaj.jar;${JBOSS.endorsed}\jbossws-native-jaxrpc.jar;${JBOSS.endorsed}\jbossws-native-jaxws.jar
[I was using ANT for this so JBOSS.endorsed would be the full path to JBOSSHOME/lib/endorsd.]
this prepends the bootclasspath to look in the jars in the lib/endorsed folder of JBOSS before the JDK rt.jar.
This takes the
soap msg error away but for some reason
you should get a logger classDefnotFound error.
To get rid of this just make sure you insert
jboss-logging-spi.jar from JBOSS_HOME/client to JBOSS_HOME/lib/endorsed
I made sure also that jbossws-native-[saaj/jaxrpc/jaxws/jaxws-ext.jar] and jaxb-api are also in teh lib/endorsed folder
That should do it!!
Hope this works for you! it was a HUGE pain in the ass for me :/
-D