It's not newer or older URIs -- one refers to xsd:string, the other
refers to soapenc:string. They are different types (soapenc:string is
nillable; xsd:string isn't nillable unless you specifically state that
it is). Per the SOAP spec, RPC/encoded messages "should" use
soapenc:string, but the interpretation of the spec is less than
perfect. Most systems use xsd:string instead. In this case, Sun
JAX-RPC is expecting xsd:string, but Axis is sending a soapenc:string.
There's a fix for Axis to make it use xsd:string instead.
Anne
On 6/28/05, Nikita Tovstoles <[EMAIL PROTECTED]> wrote:
> I'm getting the following error while executing a wsdl2java-produced
> client against a web service with WSDL produced by wscompile (with
> netbeans 4.1):
>
> JAXRPCTIE01: caught exception while handling request: deserialization
> error: unexpected element type:
> expected={http://www.w3.org/2001/XMLSchema}string,
> actual={http://schemas.xmlsoap.org/soap/encoding/}string
>
> wscompile-produced WSDL seems to use URI
> http://schemas.xmlsoap.org/soap/encoding/ for definition of common
> types (int, string etc), while wsdl2java seems to prefer
> http://www.w3.org/2001/XMLSchema. Should I somehow wsdl2java to use the
> earlier URI? In general, is it a bad idea to generate service WSDL with
> wscompile and consume with axis?
>
> thanks
> -nikita
>
>
>
>
