Make sure your .NET proxy class thinks its doing section 5 encoding,
it sounds like its trying to do doc/literal.

The method in the proxy class should have a
System.Web.Services.Protocols.SoapRpcMethodAttribute attribute on it.

Cheers
Simon
www.pocketsoap.com

On Fri, 25 Jan 2002 09:25:04 +0100, in soap you wrote:

>Hi All!
>
>I have got a interoperability problem between a MS.NET client and Apache 
>SOAP server. The problem is that there are no namespace prefixes in the 
><return> element(s) of the RPC response from the Apache SOAP server.
>
><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:HelloWorldResponse xmlns:ns1="http://sicher.net/"; 
>SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
>     <return xsi:type="xsd:string">HelloWorld</return>
></ns1:HelloWorldResponse>
></SOAP-ENV:Body>
></SOAP-ENV:Envelope>
>
>The .NET client does not recognize that the <return> element.
>
>If I use my own serializer to serialize this message and put the 
>namespace prefix infront of the <return> tag (<ns1:return>) the .NET 
>client recognizes the <ns1:return> element.
>
><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:HelloWorldResponse xmlns:ns1="http://sicher.net/"; 
>SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/";>
>     <ns1:return xsi:type="xsd:string">HelloWorld</return>
>     ^^^^^
></ns1:HelloWorldResponse>
></SOAP-ENV:Body>
></SOAP-ENV:Envelope>
>
>I have looked through the Apache SOAP source code, but it seems there is 
>no possibility to enable the namespace prefix other than writing my own 
>serializer.
>
>
>Are there any possiblities to get the .NET client to accept the return 
>element without the namespace prefix, or are there other possibilies 
>then writing my own serializers?
>
>
>cu
>lot

Reply via email to