Yes, it's a classpath problem. The JAX-WS provider is accessed by a Jar service loader. Depending on which jar is in the classpath it either loads the Jbossws one or the Sun RI one: com.sun.xml.ws.spi.ProviderImpl. It's the two jars pramod_bs described. They only needed for the wsconsume and wsprovide tools, but shouldn't be on the client classpath. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141094#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...