lt;[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 10, 2005 4:03 PM
Subject: Re: calling MessageService sample with .NET client
For easiest interoperability with .NET, I suggest you use the "wrapped"
style.
.NET does allow you to send raw XML, but to do so you ha
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> name="echoElementsResponse"/>
>
>
>
>
>
> type="impl:GoogleAccessConnector">
>
> transport="http://schemas.xmlsoap.org/soap/http"/>
>
soap/http"/>
http://localhost:7001/axis/services/GoogleAccessConnector"/>
- Original Message -
From: "Paul Callahan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 10, 2005 12:16 PM
Subject: Re: calling Mes
Praveen,
This really depends on how you have structured your wsdl for the
service. If you are using message style services, then in most cases,
you are providing your own XML Schema to define the types that are
passed via the method you expose as a "message-based" service.
Whether you use JAXB,
I have looked at the MessageService sample (both
server and the client). It passes Element[] as the argument and also returns the
same. This is fine for java based clients. But if I want to invoke it using non
java clients like .NET, how does it work? Are Axis's "message-style" services
inte
