Hi Alessio,
I tried including both 'org.jboss.ws.jaxws-client services export' and 'org.jboss.ws.cxf.jbossws-cxf-client services export' in the dependences list but neither resolved the problem I had on the client side. When I looke dfurther into ti I realised that there is no service.xml override for the XPathFactory in the jbossws and cxf jars. The client fault handling code relies upon loading the hardwired fallback implementation class, com.sun..org.apache.xpath.internal.jaxp/XPathFactory, which is in rt.jar. This means that one of the jbossws or cxf modules needs to inport and then re-export it. I patched myrelease by adding the following to the dependencies set in module.xml file in modules/org/jboss/ws/jbossws-cxf-client/main
<module name="system" export="false">
<imports>
<include-set>
<path name="com/sun/org/apache/xpath/internal/jaxp"/>
</include-set>
</imports>
<exports>
<include-set>
<path name="com/sun/org/apache/xpath/internal/jaxp"/>
</include-set>
</exports>
</module>
This ensures that ClientFaultConverter can see the hard-wired XPathFactory implementation.
This now means that all the XTS unit tests are running correctly which is great. I still have to get the XTS interop tests (our client against our server) and XTS demo to work but it's looking very good so far so I'm hoping they will present no further hurdles.