More detective work is needed here: 1.) Are you using an rpc/encoded web service, instead of doc/lit or rpc/lit (Can you show us a part of the wsdl:binding section, that's where you can determine that)--if so, that is not supported by jax-ws. For rpc/encoded, you'll need to use the Dispatch object or SAAJ instead.
An RPC/encoded sample using Dispatch object is here: http://www.jroller.com/gmazza/date/20071102 2.) You may wish to use both Metro and CXF when working with SOAP clients, because, depending on whether or not it fails on both stacks, that helps pinpoint if the problem is (1) with the web service stack or (2) your own code. If (2), frequently different error messages are given by the two stacks, which can help greatly in troubleshooting the problem with the client code. The "run-client" target of step 5 here[1] shows how this can be done. All that is needed is to switch the <path refid.../> between "cxf.classpath" and "metro.classpath" to activate the different web service stack. Recompiling is not necessary, because JAX-WS artifacts are interoperable between web service stacks. [1] http://www.jroller.com/gmazza/date/20070817 HTH, Glen Am Montag, den 12.11.2007, 04:44 -0800 schrieb JoCosti: > Hi there, > > I'm using 2.0.2 version to generate the client side of an existing web > service. > I have already managed to write a client with another framework using > jax-rpc technology, I nowwant to migrate to jax-ws with CXF framework > > When running the client web service, I'm facing the following exception : >
