The Web service will expose a WSDL, like any other. From this point, you can (mostly*) ignore the fact that the service is implemented in ASP.net.
Then, implement it like any other Web service. This recent thread had some links for this.
When accessing a Web service produced using a toolkit other than the one you're using, it's quite possible you'll run into difficulties/bugs/inconsistencies. There are some documented problems between Microsoft platforms and Java ones, such as Microsoft's use of 'Document/Literal Wrapped', which is non-standard. Googling with the appropriate terms will find a horde of relevant sites.
Joined: Dec 14, 2004
here's a description of the service deployed in ASP.NET . I need a java Client to access this service. After writing a java client i have not been able to get the desired result. im getting an exception as follows ____________________________________________________________________________ Exception in thread "main" java.io.IOException: Server returned HTTP response code: 500 for URL: http://127.0.0.1/test/HelloWorld.asmx/add at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon nection.java:697) at Client.main(Client.java:45)____________________________________________________________________________
The listing of the add method(ASP.NET) is as follows
SOAP The following is a sample SOAP request and response. The placeholders shown need to be replaced with actual values.