Check Scott's tutorial at http://www.scottnichol.com/vbclientapachesoap.htm
- Jasen.
P.S. I solved my problem of MS and Apache clients talking to MS and Apache servers with just an end point URL change. The solution involves 1) Modifying the MS WSDL to set the return type on all methods to "xsd:anyType" - that will tell the MS server to return type info. 2) Set the SOAP Action in the MS WSDL to "" - that will comply with Apache server's ignoring the SOAP Action. (And then you must use MSTK 3 as 2 REQUIRES the SOAP Action to be non-empty.) 3) Setting the SOAP body namespace in the MS WSDL to the deployed ID of the service in Apache.
Using this method, one can use the ISAPI server on MS. Then both MS and Apache use a common end point URL - the ISAPI SOAP directory for MS; the rpcrouter for Apache. The target object URI (this is the SOAP body namespace) is used to identify the class to invoke. The method is the method. And the SOAP Action is not used. (Well, technically, it is, but it's empty and the same for all services so it's not really used to resolve the service to invoke.)
> -----Original Message-----
> From: Earl Bingham [mailto:[EMAIL PROTECTED]]
> Sent: Friday, June 14, 2002 1:04 PM
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: Apache SOAP client MS SOAP server?
>
>
>
> What about examples of MS SOAP Clients communicating with an
> Apache SOAP
> Server?
>
> - Earl
