"crussell42" wrote : I was getting something similar and needed to point my runtime classpath at jboss/client jars. | | SO Here was the fix to make sure the jboss/client/*.jar is in classpath first. Is that so? Looking at examples/common/ws-build.xml, the run-test target references a test.path defined near the top of the file: <path id="test.path"> | <path refid="jboss.path" /> | <pathelement location="${common.classes.dir}" /> | <pathelement location="${output.classes.dir}" /> | </path> In turn, jboss.path points to the jboss client jars: <path id="jboss.path"> | <pathelement location="${common.config.dir}" /> | <fileset dir="${jboss.home}/client" includes="*.jar" /> | </path> To me, it looks like the jdk1.5 xml apis were not endorsed properly. If you look at jboss/lib/endorsed/xml-apis.jar, the QName class there has a serialVersionUID equal to 4418622981026545151. Conversely, in jdk1.5 it is -9120448754896609940. Hence the client and server classes are different. Meghana, what directory did you copy the endorsed jars to? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013207#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...