This use case illustrates how to use XrML in a service-centric business model, which focuses on specifying rights, conditions, and metadata for services, such as web services. In this use case, Alice pays $2.00 each time she uses a web service to receive stock quotes. The following figure illustrates this use case:

This Appendix shows an example of a dynamic client application that does not use the WSDL file when it invokes a WebLogic Web Service.

The example below is of a WSDL document generated by JDeveloper for a simple web service which returns the current date and time as a string. It provides an illustration of the structure of a WSDL document.

Web Service Tutorial/Examples.

Web service example of Hello World.

Following is the WSDL file that is provided with Cape Clear as part of the stock demonstration program. When a company name is specified, the program consults a database and returns the company’s current stock price.

We're finally ready to implement the Grid Service. Since its behaviour is exactly the same as the previous example, the implementation is practically the same:

Create a new document from a Query-Error-Response template. (This helps us with our simple example as it already sets up a webservice connector and a submit button in the form.

A WSDL description of a "stock quote" service:

To test the server implementation of Spheon JSOAP, we set up a a server with a few webservices. If you find any bugs or incompatibilities, please send me an Email.

XML and SOAP Examples

Gecko WSDL Example - Babel Fish

In example 1 of WSDL 1.1 (2001-03-15) the binding reference from the port does not resolve because of a typo. The binding name should be:

One of the best aspects of WSDL is that you rarely have to create WSDL files from scratch. A whole host of tools currently exists for transforming existing services into WSDL descriptions. You can then choose to use these WSDL files as is or manually tweak them with your favorite text editor. In the discussion that follows, we explore the WSDL generation tool provided by GLUE.

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.

HelloServiceEJB is a stateless session bean that implements a single method, sayHello. This method matches the sayHello method invoked by the clients described in Creating Web Service Clients with JAX-RPC. Later in this section, you'll test the HelloServiceEJB by running one of these JAX-RPC clients.

Mozilla has built functions called XML Extras that allow the use of XML as data in both JavaScript and C++. Such functions are an XML Serializer, XMLHttpRequest, XML Parser, SOAP-based RPC, and XML Persistence. You can find more information about these functions, along with examples, at http://www.mozilla.org/xmlextras/.

Mark Pilgrim's article about web services in Python contains one important bit that is often overlooked by people implementing web services with XML-RPC, the listMethods extension. The Python XML-RPC ServerProxy Objects documentation explains each method: listMethods(), methodSignature(), and methodHelp().

The wsdl2java utility automatically generates Java data structures for complex types in a WSDL file, with full support for inheritance. Each data structure contains a set of public fields and implements java.io.Serializable. To generate public accessors and private fields, use the -g option. When you invoke the web service, the Glue runtime automatically maps the Java to/from XML. The rules for how Glue does this are described in the Java/XML Mapping section.

Glue supports most of servlets 2.3. The Glue servlet implementation is not complete yet, and is therefore not officially compatible with the specification. webMethods is in the process of licensing the servlet TCK from Sun in order to pass the compatibility tests. The current limitations of our servlet implementation are listed at the end of this section.