You need to create a WSDL description of your service. A .NET client should be able to automatically consume a WSDL file and talk to the Web service, although interoperability between .NET and Apache SOAP can sometimes be problemmatic.
I suggest that you use the Apache Axis java2wsdl tool to generate your WSDL file. Actually, since you're first starting out, I recommend that you switch from Apache SOAP to Apache Axis entirely. Apache Axis is the new and improved version of Apache SOAP. It has native support for WSDL. It supports much easier interoperability with .NET and other systems. It supports the JAX-RPC API standard. It's lots faster. And it's much easier to use. See http://ws.apache.org/axis. Anne ----- Original Message ----- From: "Parames" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, June 17, 2003 11:33 PM Subject: Webservices for ASP dot net client > Hi folks , > Im not good in soap and have done few examples using > Tomcat and SOAP2.3.1 thatsall ,i need a favour . > > Now i want my services to talk to ASP dot net client.. > How shalli proceed?? > Any examples??? > > Please take me to the right path > Thanks and regards > > > __________________________________ > Do you Yahoo!? > SBC Yahoo! DSL - Now only $29.95 per month! > http://sbc.yahoo.com
