When planning to use a new Web service, you need to learn its interface first. You can learn it from the Web service's WSDL (Web Services Description Language) document. It describes the messages that the Web service understands, the format of its responses to those messages, the protocols that the service support, and so on.

What and why WSDL ?

These are very approximate, only intended to try and get a feel for what they might turn out like. All should support other services/formats directly, except the AtomAPI, which presumably would need external services placing in other namespaces.

This is a simple example that will show you how to develop a Web Servic client and service starting from a WSDL document. The flow of this example is very similar to the hello example with RMI because RMI and WSDL have same function as a contract between client and server. Again, the development process can be divided into the following steps:

The WSDL Specification

Using WSDL in a UDDI Registry

The following example use's AMFPHP and nusoap to consume two different web services inside of flash. Below is a brief overview, however this application is meant mainly for sample code.

Web Services Introduction

Introduction to WSDL

WSDL is a specification defining how to describe web services in a common XML grammar. WSDL describes four critical pieces of data:

A Profile-based class hierarchy of service categories.

QoS for B2B Commerce - In the new Web Services Economy

Our initial discussion of WSDL invocation tools focused on programming and command-line invocation tools. We now move on to even simpler tools that are entirely driven by a web-based interface.

In a previous article I explained how to use Soap Extensions to extend and customize the process of sending and receiving Soap messages. But for all this to work, the server needs to tell the client which extensions it is using. The place to declare this information is the WSDL document, the document that acts as a contract between de client and the server.

A pdf which covers demystifying service oriented architecture.

This powerpoint presentation shows verious details about WSDL.

This section shows an example of how to PocketSOAP to call the XSpace service using Visual Basic.

This tutorial describes the ServiceDesigner sView service, and the service location web site Salcentral.com.

The SOAPworX code generator can generate client and server code separately, or at the same time. In this example, we will generate both the client and the server.

The following example is similar to the preceding example, but instead of specifying the city argument in the URI of the resource, the argument is passed when calling the resource.