Client sends incomplete SOAP-Request

[Martin Hey]

I'm consuming an AXIS-webservice. Therefore I got the WSDL.
I added a new web reference to my project pointing to this WSDL.

In Visual Studio I can use all objects the webservice returns and The
service responds to all requests. But there is also a method I have to send
one of the complex types defined in WSDL. And there is the problem. The
SOAP-Request contains no type-information and so the service is not able to
deserialize the objects sent.

my request contains:
<User><name>Barth</name><vorname>Simon</vorname></User>

the service expects:
<multiRef id="id0" soapenc:root="0"
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xsi:type="ns4:User"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns4="urn:UserSync">
<name xsi:type="xsd:string">Barth</name>
<vorname xsi:type="xsd:string">Simon</vorname>
</multiRef>

Where am I able to influence this behaviour? The provider of the service
says these type informations are essential....

[Mr. Arnold]

"Martin Hey" <ma*******@kaffeeschluerfer.comwrote in message
news:E7**********************************@microsof t.com...

I'm consuming an AXIS-webservice. Therefore I got the WSDL.
I added a new web reference to my project pointing to this WSDL.

In Visual Studio I can use all objects the webservice returns and The
service responds to all requests. But there is also a method I have to
send one of the complex types defined in WSDL. And there is the problem.
The SOAP-Request contains no type-information and so the service is not
able to deserialize the objects sent.

my request contains:
<User><name>Barth</name><vorname>Simon</vorname></User>

the service expects:
<multiRef id="id0" soapenc:root="0"
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
xsi:type="ns4:User"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:ns4="urn:UserSync">
<name xsi:type="xsd:string">Barth</name>
<vorname xsi:type="xsd:string">Simon</vorname>
</multiRef>

Where am I able to influence this behaviour? The provider of the service
says these type informations are essential....

You need a Type.XSD to explain the types, which the service provider should
have provided to you. If you have a problem, you need to get back in touch
with the provider to explain, provide information and help in making or
using their Web service.