• Web Service Description Language (WSDL) 1.1

• Web Services Description Language (WSDL) Version 2.0 Part 0: Primer                                                           http://www.w3.org/TR/2004/WD-wsdl20-primer-20041221/
  

• Web Service Description Language (WSDL) Version 2.0 Part 1:Core Language                                                                                           http://www.w3.org/TR/wsdl20
  

• Web Services Description Language (WSDL) Version 2.0 Part 2: Predefined Extensions                                                                       http://www.w3.org/TR/wsdl20-extensions/
  

• Web Services Description Language (WSDL) Version 2 Part 3: Bindings // W3C Working Draft                                                              http://www.w3.org/TR/wsdl20-bindings
  

<?xml version="1.0"?>
<definitions name="StockQuote"

targetNamespace="http://example.com/stockquote.wsdl"
          xmlns:tns="http://example.com/stockquote.wsdl"
          xmlns:xsd1="http://example.com/stockquote.xsd"
          xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
          xmlns="http://schemas.xmlsoap.org/wsdl/">

    <types>
       <schema targetNamespace="http://example.com/stockquote.xsd"
              xmlns="http://www.w3.org/2000/10/XMLSchema">
           <element name="TradePriceRequest">
              <complexType>
                  <all>
                      <element name="tickerSymbol" type="string"/>
                  </all>
              </complexType>
           </element>
           <element name="TradePrice">
              <complexType>
                  <all>
                      <element name="price" type="float"/>
                  </all>
              </complexType>
           </element>
       </schema>
    </types>

    <message name="GetLastTradePriceInput">
        <part name="body" element="xsd1:TradePriceRequest"/>
    </message>

    <message name="GetLastTradePriceOutput">
        <part name="body" element="xsd1:TradePrice"/>
    </message>

    <portType name="StockQuotePortType">
        <operation name="GetLastTradePrice">
           <input message="tns:GetLastTradePriceInput"/>
           <output message="tns:GetLastTradePriceOutput"/>
        </operation>
    </portType>

    <binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <operation name="GetLastTradePrice">
           <soap:operation soapAction="http://example.com/GetLastTradePrice"/>
           <input>
               <soap:body use="literal"/>
           </input>
           <output>
               <soap:body use="literal"/>
           </output>
        </operation>
    </binding>

    <service name="StockQuoteService">
        <documentation>My first service</documentation>
        <port name="StockQuotePort" binding="tns:StockQuoteBinding">
           <soap:address location="http://example.com/stockquote"/>
        </port>
    </service>

</definitions>

WSDL Major Elements

Since it will be some time before WSDL 2.0 support is widespread we 
will focus on describing WSDL 1.1 elements and note where WSDL 2.0
differs from WSDL 1.1. 

The <definitions> Element

The 'definitions' element is the root element of a WSDL document. It holds 
all other WSDL elements. The element has a 'name' attribute that normally 
corresponds to the name of the WebService. It has a 'targetNamespace' 
attribute for the document. The definitions element will also contain a number 
of related namespaces such as those for SOAP and WSDL. An XML schema 
namespace may appear in the 'definitions' element or locally in the 'types'
element, (as observed in various examples). 

The following set of namespaces from the Apache Axis WSDL example
shows an interesting  variation where a URNs are used in a couple of 
namespace declarations. Also note that SOAP 1.1 is being targeted 
as is the 1.1 version of WSDL. 

The following is a skeleton representation of a <definitions> element
with it's potential constituent parts. 

A <definitions> element Skeleton Diagram

<definitions name="UsuallyNameOfWebService" 
            targetNamespace = "http://www.example.com/services/ServiceNamespace"     
        <!-- also normally includes SOAP, WSDL and optionally XML Schema namespaces>
                >
<!-- All the following elements may appear zero or more times 
      except for the 'types' element which appears zero or one times >
   
     <documentation/>  
     <import />             
     <types />
     <message> 
     <portTypes />        
     <binding />           
     <service />
     <binding  />
     <service />    

</definitions>         


WSDL 2. Differences 

The <definitions> element of WSDL1.1 is replaced by the <descriptions> 
element and it's sub-elements in WSDL 2.0. 


The <document> Element

WSDL uses the 'document' element to provide readable documentation 
for human use.  The document is a mixed type allows arbitrary text and 
element mixing and is allowed inside any WSDL language element. 


The <import> Element

The original authors of WSDL promoted 'modularity', supplying the 'import' 
element to allow defining different aspects of an overall WSDL description 
in separate documents. These documents could then be imported into larger 
WSDL document. You can imagine this would be handy for a schema 
document for instance. The 'import' element has the following form. 
The folloiwng form as described in the W3C WSDL 1.1 Note shows that
the import element allows a namespace and a location to be specified
for a document via URIs. 


The <import> element Form 

    <import namespace="uri" location="uri"/> *


WSDL 1.1 Note Example

 <import namespace="http://example.com/stockquote/schemas"
           location="http://example.com/stockquote/stockquote.xsd"/>


The <types> Element

  <!-- type defs -->

  <types>
    <xsd:schema targetNamespace="urn:AddressFetcher2"
                xmlns:xsd="http://www.w3.org/1999/XMLSchema">

      <xsd:simpleType name="stateType">
        <xsd:restriction base="xsd:string">
            <xsd:enumeration value="TX"/>                      
            <xsd:enumeration value="IN"/>
            <xsd:enumeration value="OH"/>                    
        </xsd:restriction>
      </xsd:simpleType>

      <xsd:complexType name="phone">
        <xsd:all>
            <xsd:element name="areaCode" type="xsd:int"/>
            <xsd:element name="exchange" type="xsd:string"/>
            <xsd:element name="number" type="xsd:string"/>
        </xsd:all>
      </xsd:complexType>

      <xsd:complexType name="address">
        <xsd:all>
            <xsd:element name="streetNum" type="xsd:int"/>
            <xsd:element name="streetName" type="xsd:string"/>
            <xsd:element name="city" type="xsd:string"/>
            <xsd:element name="state" type="typens:stateType"/>
            <xsd:element name="zip" type="xsd:int"/>
            <xsd:element name="phoneNumber" type="typens:phone"/>
        </xsd:all>
      </xsd:complexType>
    </xsd:schema>
  </types>

The <message> Element

// The message-typing attributes (which may vary depending
// on the type system used) are shown in bold. - WSDL 1.1 Note

W3C Form of the <portType> Element  

<wsdl:definitions .... >
    <wsdl:portType name="nmtoken">
        <wsdl:operation name="nmtoken" .... /> *
    </wsdl:portType>
</wsdl:definitions>

<wsdl:definitions .... >
    <wsdl:binding name="nmtoken" type="qname"> *
        <-- extensibility element (1) --> *
        <wsdl:operation name="nmtoken"> *
           <-- extensibility element (2) --> *
           <wsdl:input name="nmtoken"? > ?
               <-- extensibility element (3) --> 
           </wsdl:input>
           <wsdl:output name="nmtoken"? > ?
               <-- extensibility element (4) --> *
           </wsdl:output>
           <wsdl:fault name="nmtoken"> *
               <-- extensibility element (5) --> *
           </wsdl:fault>
        </wsdl:operation>
    </wsdl:binding>
</wsdl:definitions>

You'll notice what seems to be a little redundancy as the binding element
maps information to each of the operations and their parts. The 'binding' 
element supplies protocol-specific information for each of the elements 
of a 'portType' definition. 

There is one other element that is added to the binding element that is specific
to SOAP. In the case of SOAP it is the <soap:binding> element. The style 
attribute can hold either the value "rpc" or "document to describe the messaging 
format. In the following example, "rpc", and the transport protocol, in the following  
example it is HTTP. 


First Few Lines of the <binding> Element in the Apache Axis WSDL Example 

 <binding name="AddressBookSOAPBinding" type="tns:AddressBook">
    <soap:binding style="rpc"
                  transport="http://schemas.xmlsoap.org/soap/http"/>


The 'style' attribute is important as it decides what format the SOAP messaging
will take. If the 'style' is 'document' type then the message goes 'as is' in the 
SOAP envelope. If the "rpc" value is specified then messages are nested in 
the context of operation elements. 

  <binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <operation name="GetLastTradePrice">
           <soap:operation soapAction="http://example.com/GetLastTradePrice"/>
           <input>
               <soap:body use="literal"/>
           </input>
           <output>
               <soap:body use="literal"/>
           </output>
        </operation>
    </binding>

The <service> Element

A service encapsulates a group of zero or more related ports. Ports
defined in a service are restricted from inter-communicating. Ports
may be supplied that are the same port type but use different bindings
or addresses. In this case these ports are considered alternatives,
supplying the same service over different transport protocols and
message formats.

W3C Grammar for the <service> Element

<wsdl:definitions .... >
    <wsdl:service name="nmtoken"> *
        <wsdl:port .... />*
    </wsdl:service>
</wsdl:definitions>



The <port> Element

The port element is used supply an address for a web service. It does
this by defining an endpoint. For a given binding, a single address is 
specified. Following is the W3C description of the grammar used for 
the 'port' element. 

W3C Grammar for the <port> Element

  <service name="StockQuoteService">
        <documentation>My first service</documentation>
        <port name="StockQuotePort" binding="tns:StockQuoteBinding">
           <soap:address location="http://example.com/stockquote"/>
        </port>
    </service>

// the binding attribute references the WSDL documents <binding> element

WSDL Transmission Primitives

WSDL defines four types of operations which are termed 'transmission
primitives' that parallel the messaging formats that are described in 
SOAP. They are 'one-way', 'request-response', 'solicit-response' and 
'notification'. The WSDL 1.1 note only defines the first two bindings. 
The latter two are described but not implemented. 

WSDL Transmission Primitives

• One-way  // endpoint receives a message
  
• Request-Response. // receiving and sending a message
  
• Solicit-Response. // an endpoint sends a message and receives a response
  
• Notification. // endpoint sends a message
  

One-way Operation

The one-way operation is characterized by a single input element.

W3C 'One-way' Operation Grammar

The input element specifies the abstract message format for the one-way operation.

Request-response Operation

The grammar for a solicit-response operation is:

The grammar of the notification operation mirrors the one-way operation similar in that
it has a single but opposite 'output' element nested.

// If a part name appears in only the input message, it is an 'in' parameter.
// If a part name appears in only the output message, it is an 'out' parameter
// A part name that appears in both the input and output message, it is named an 'in/out' parameter

WSDL Use of the 'import' Element

The W3C WSDL note supplies an example based on it's first example
to show how the data type definitions, the abstract definitions and the
specific bindings can be separated into separate documents.

WSDL 1.1 Note Schema Definition Example

// has the URL, http://example.com/stockquote/stockquote.xsd

<?xml version="1.0"?>
<schema targetNamespace="http://example.com/stockquote/schemas"
       xmlns="http://www.w3.org/2000/10/XMLSchema">
       
    <element name="TradePriceRequest">
        <complexType>
            <all>
                <element name="tickerSymbol" type="string"/>
            </all>
        </complexType>
    </element>
    <element name="TradePrice">
        <complexType>
            <all>
                <element name="price" type="float"/>
            </all>
        </complexType>
    </element>
</schema>

The above schema is imported into the following WSDL document
that focuses on defining the abstract aspects of a WSDL definition,
the description of the interface (portType), operations and messages.

WSDL 1.1 Note Defining the Abstract Aspects of the Service

// http://example.com/stockquote/stockquote.wsdl

<?xml version="1.0"?>
<definitions name="StockQuote"

targetNamespace="http://example.com/stockquote/definitions"
          xmlns:tns="http://example.com/stockquote/definitions"
          xmlns:xsd1="http://example.com/stockquote/schemas"
          xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
          xmlns="http://schemas.xmlsoap.org/wsdl/">

   <import namespace="http://example.com/stockquote/schemas"
           location="http://example.com/stockquote/stockquote.xsd"/>

    <message name="GetLastTradePriceInput">
        <part name="body" element="xsd1:TradePriceRequest"/>
    </message>

    <message name="GetLastTradePriceOutput">
        <part name="body" element="xsd1:TradePrice"/>
    </message>

    <portType name="StockQuotePortType">
        <operation name="GetLastTradePrice">
           <input message="tns:GetLastTradePriceInput"/>
           <output message="tns:GetLastTradePriceOutput"/>
        </operation>
    </portType>
</definitions>


Finally, the Interface WSDL document is imported into a WSDL 
document that supplies the concrete implementation details, in 
the <binding> and <service> elements. 


W3C WSDL 1.1 Note Example Importing PortType into a WSDL 
Document Defining The Bindings and Service

// http://example.com/stockquote/stockquoteservice.wsdl

<?xml version="1.0"?>
<definitions name="StockQuote"

targetNamespace="http://example.com/stockquote/service"
          xmlns:tns="http://example.com/stockquote/service"
          xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
          xmlns:defs="http://example.com/stockquote/definitions"
          xmlns="http://schemas.xmlsoap.org/wsdl/">

   <import namespace="http://example.com/stockquote/definitions"
           location="http://example.com/stockquote/stockquote.wsdl"/>

    <binding name="StockQuoteSoapBinding" type="defs:StockQuotePortType">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <operation name="GetLastTradePrice">
           <soap:operation soapAction="http://example.com/GetLastTradePrice"/>
           <input>
               <soap:body use="literal"/>
           </input>
           <output>
               <soap:body use="literal"/>
           </output>
        </operation>
    </binding>

    <service name="StockQuoteService">
        <documentation>My first service</documentation>
        <port name="StockQuotePort" binding="tns:StockQuoteBinding">
           <soap:address location="http://example.com/stockquote"/>
        </port>
    </service>
</definitions>

The following points are quoted from the W3C WSDL note primarily to
show the parts of the WSDL document that are involved in binding the
message to the underlying protocol. The examples are easy to view
as the pertinent sections are highlighted.

The first example shows a document style communication over SMTP.
You can see the style is assigned the "document" value and the use
attributes are assigned "literal" values. In this case the 'transport'
attribute is assigned the URL representing SMTP, "

Example   transport="http://example.com/smtp"

W3C Example  SOAP binding of one-way operation over SMTP using a SOAP Header
// from the W3C WSDL note

<?xml version="1.0"?>
<definitions name="StockQuote"
          targetNamespace="http://example.com/stockquote.wsdl"
          xmlns:tns="http://example.com/stockquote.wsdl"
          xmlns:xsd1="http://example.com/stockquote.xsd"
          xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
          xmlns="http://schemas.xmlsoap.org/wsdl/">

    <message name="SubscribeToQuotes">
        <part name="body" element="xsd1:SubscribeToQuotes"/>
        <!-- an example of a Header Definition -->
        <part name="subscribeheader" element="xsd1:SubscriptionHeader"/>
    </message>

    <portType name="StockQuotePortType">
        <operation name="SubscribeToQuotes">
           <input message="tns:SubscribeToQuotes"/>
        </operation>
    </portType>

    <binding name="StockQuoteSoap" type="tns:StockQuotePortType">
        <soap:binding style="document" transport="http://example.com/smtp"/>
        <operation name="SubscribeToQuotes">
           <input message="tns:SubscribeToQuotes">
               <soap:body parts="body" use="literal"/>
               <soap:header message="tns:SubscribeToQuotes" part="subscribeheader" use="literal"/>
           </input>
        </operation>
    </binding>

    <service name="StockQuoteService">
        <port name="StockQuotePort" binding="tns:StockQuoteSoap">
           <soap:address location="mailto:subscribe@example.com"/>
        </port>
    </service>

    <types>
        <schema targetNamespace="http://example.com/stockquote.xsd"
               xmlns="http://www.w3.org/2000/10/XMLSchema">
           <element name="SubscribeToQuotes">
               <complexType>
                   <all>
                       <element name="tickerSymbol" type="string"/>
                   </all>
               </complexType>
           </element>
           <element name="SubscriptionHeader" type="uriReference"/>
        </schema>
    </types>
</definitions>

<?xml version="1.0"?>
<definitions name="StockQuote"
          targetNamespace="http://example.com/stockquote.wsdl"
          xmlns:tns="http://example.com/stockquote.wsdl"
          xmlns:xsd="http://www.w3.org/2000/10/XMLSchema"
          xmlns:xsd1="http://example.com/stockquote.xsd"
          xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
          xmlns="http://schemas.xmlsoap.org/wsdl/">

    <message name="GetTradePriceInput">
        <part name="tickerSymbol" element="xsd:string"/>
        <part name="time" element="xsd:timeInstant"/>
    </message>

    <message name="GetTradePriceOutput">
        <part name="result" type="xsd:float"/>
    </message>

    <portType name="StockQuotePortType">
        <operation name="GetTradePrice">
           <input message="tns:GetTradePriceInput"/>
           <output message="tns:GetTradePriceOutput"/>
        </operation>
    </portType>

    <binding name="StockQuoteSoapBinding" type="tns:StockQuotePortType">
        <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
        <operation name="GetTradePrice">
           <soap:operation soapAction="http://example.com/GetTradePrice"/>
           <input>
               <soap:body use="encoded" namespace="http://example.com/stockquote"
                          encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
           </input>
           <output>
               <soap:body use="encoded" namespace="http://example.com/stockquote"
                          encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
           </output>
        </operation>>
    </binding>

    <service name="StockQuoteService">
        <documentation>My first service</documentation>
        <port name="StockQuotePort" binding="tns:StockQuoteBinding">
           <soap:address location="http://example.com/stockquote"/>
        </port>
    </service>
</definitions>

% java org.apache.axis.wsdl.Java2WSDL -o wp.wsdl  
    -l"http://localhost:8080/axis/services/WidgetPrice" -n  "urn:Example6" 
    -p"samples.userguide.example6" "urn:Example6"  samples.userguide.example6.WidgetPrice

Where:

• -o indicates the name of the output WSDL file
• -l indicates the location of the service
• -n is the target namespace of the WSDL file
• -p indicates a mapping from the package to a namespace. There may be multiple mappings.
• the class specified contains the interface of the webservice.

Note on associating JSWSDP with Tomcat After Installation 

The Java Development Kit link to get version 5. 

http://java.sun.com/j2se/1.5.0/download.jsp

Install as usual.


2 )  Install Apache Tomcat as usual. 
http://jakarta.apache.org/site/binindex.cgi#Release%20Builds


3) The JWSDP package expands in typical Sun fashion.  You will encounter
that there are two ways of installing the java web services package. This 
will come at you as the JWSDP wizard proceeds.

If you have Apache Tomcat already installed, the Java Web Services
package wizard can be directed to automatically use it as it's web server.
On my home machine, I had trouble getting the wizard to accept the location
I had for Tomcat so I elected to make the connection between Tomcat and
Java Web Services after the fact using the script described below.  
Following
is the JWSDP download. 

*To Test:* Before you install the JWSDP, and you open  on Tomcat at
http://localhost:8080 you will see the regular Tomcat Welcome page. 
After installing the JWSDP.  (either connecting JWSDP to Tomcat
at running the wizard or after using the script) you will see a different
Welcome page when opening on localhost:8080.  This tells you the
install is successful and Apache Tomcat is ready to run the web
services stuff.


    Java Web Services Developer Pack 1.5 Download

http://java.sun.com/webservices/downloads/webservicespack.html



*Joining Java Web Services to Tomcat After Installation Using the Script*

To join the Web Services stuff to Tomcat after you have JWSDP installed
you need to run a Web Services Script. 

After the JWSDP is expanded, you will find a 'jwsdpontomcat' script
under the following directories.  

jwsdp-1.5  \ jwsdp-shared \  bin \ jwsdpontomcat.bat / // windows/

jwsdp-1.5 / jwsdp-shared /  bin / jwsdpontomcat.sh  /// solaris/ linux /

Run and if things go well it ends saying BUILD SUCCESSFUL.
.