M
Marc Landrum
I am trying to connect to JAX-RPC webservice where the webservice is using
the "http://schemas.xmlsoap.org/soap/encoding/" namespace for primitive
datatypes like string or float instead of "http://www.w3.org/2001/XMLSchema".
Regardless of how the WSDL defining the webservice is formatted, the .NET
webservice proxy will always use the "http://www.w3.org/2001/XMLSchema"
namespace for all primitive data types. JAX-RPC will reject the request with
an error such as:
JAXRPCTIE01: caught exception while handling request: unexpected element
type: expected={http://schemas.xmlsoap.org/soap/encoding/}string,
actual={http://www.w3.org/2001/XMLSchema}string
Is there a way to fix this at the .NET end by changing the default namespace
that is used to serialize primitive data types?
the "http://schemas.xmlsoap.org/soap/encoding/" namespace for primitive
datatypes like string or float instead of "http://www.w3.org/2001/XMLSchema".
Regardless of how the WSDL defining the webservice is formatted, the .NET
webservice proxy will always use the "http://www.w3.org/2001/XMLSchema"
namespace for all primitive data types. JAX-RPC will reject the request with
an error such as:
JAXRPCTIE01: caught exception while handling request: unexpected element
type: expected={http://schemas.xmlsoap.org/soap/encoding/}string,
actual={http://www.w3.org/2001/XMLSchema}string
Is there a way to fix this at the .NET end by changing the default namespace
that is used to serialize primitive data types?