Anne,
you were right there was a problem with the SOAP message. To address the
problem I implemented a new Web Service and a MessageReceiver that builds a
SOAP response from scratch. It worked.
I think the problem was .NET not managing to deserialise the response from
the RawXMLINOutMessageReceiver; hence my implementing a new class that
extends AbstractInOutSyncMessageReceiver.
So if anybody asks, tell them "yes, Axis2 is interoperable with .NET"
Thanks for your help,
Gobe
On Thu, 4 May 2006 19:24:52 -0400 Anne Thomas Manes wrote:
The envelope namespace should be
"http://schemas.xmlsoap.org/soap/envelope/";.
If your Axis endpoint is generating a SOAP message with a namespace of "
http://org.apache.axis2/xsd"; then you've done something wrong in your code.
Anne
On 5/4/06, GOBE HOBONA <[EMAIL PROTECTED]> wrote:
Hello,
I am attempting to run the MyService example from a Microsoft.NET client.
I
get the following SoapException from .NET when running the echo operation.
"Envelope namespace http://org.apache.axis2/xsd was unexpected. Expecting
http://schemas.xmlsoap.org/soap/envelope/";
Basically, has anybody successfully read-in SOAP objects from an Axis2 web
service to a .NET client?
Any examples of compatibility tests or programs will be much appreciated.
