Apache SOAP 2.1 and 2.2 do require xs:type attributes. You can get around
this by adding QNames for your parameters in the type mapping registry. This
is covered in the docs for Apache SOAP 2.1
Rick Hansen
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 21, 2001 12:59 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: No deserializer...
>
>
> I'm getting the following error from a MS SOAP server. My
> client is Apache
> Soap 2.1 I've read a little about the xsi:type attribute not being
> returned from MS but I thought that 2.1 did not require that...
>
> Caught SOAPException (SOAP-ENV:Client): No Deserializer found to
> deserialize a ':Result' using encoding style
> 'http://schemas.xmlsoap.org/soap/encoding/'.
>
>
> Here is the response from the server....
>
> <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
> - <SOAP-ENV:Envelope SOAP-ENV:encodingStyle
> ="http://schemas.xmlsoap.org/soap/encoding/"; xmlns:SOAP-ENV
> ="http://schemas.xmlsoap.org/soap/envelope/";>
> - <SOAP-ENV:Body>
> - <SOAPSDK1:AddResponse xmlns:SOAPSDK1="http://tempuri.org/message/";>
> <Result>15</Result>
> </SOAPSDK1:AddResponse>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> Here is what I sent in...
>
> <?xml version="1.0" encoding="UTF-8" ?>
> - <SOAP-ENV:Envelope xmlns:SOAP-ENV
> ="http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsi
> ="http://www.w3.org/1999/XMLSchema-instance"; xmlns:xsd
> ="http://www.w3.org/1999/XMLSchema";>
> - <SOAP-ENV:Body>
> - <ns1:Add xmlns:ns1="http://tempuri.org/message/";
> SOAP-ENV:encodingStyle
> ="http://schemas.xmlsoap.org/soap/encoding/";>
> <A xsi:type="xsd:int">10</A>
> <B xsi:type="xsd:int">5</B>
> </ns1:Add>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
>
> thanks
> Doug
>
