Any application can communicate with a web service if it can generate and consume XML messages and use one of the protocols supported by the target web service. This includes applications and web services built in other tools and other languages. The central reason for the development of the web service concept was to enable inter-operation of software components regardless of the operating system or language with which they are implemented. The key to this inter-operation is the WSDL file, which describes a web service in an implementation-independent way.
Visual Studio .NET can use the WSDL file of a web service to produce a web service proxy. A .NET component can then use the proxy class to communicate with the web service as though it were a local object.
Use of a WebLogic Workshop web service from an ASP.NET web service.
Non-WebLogic Workshop web service client participating in a conversation.
Non-WebLogic Workshop web service accepting a callback.
This sample is located in the interop\dotNET folder of the WebServices project in the SamplesApp sample application. In the file system the location is:
BEA_HOME\weblogic81\samples\workshop\SamplesApp\WebServices\interop\dotNET
To Run the Sample
Step by step instructions for building and running the .NET web service client may be found in the readme.html file in the interop\dotNET sample directory (above). If you are viewing this documentation on a machine running WebLogic Server in the WebLogic Workshop samples domain, you may click here to view the readme.html file.
How Do I: Communicate with a Web Service from a JSP or Servlet?
How Do I: Communicate with a Web Service from Another Java Application?
How Do I: Tell Developers of Non-WebLogic Workshop Clients How to Participate in Conversations?