| <?xml version="1.0" encoding="utf-8"?> |
| <!--Arbortext, Inc., 1988-2006, v.4002--> |
| <!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" |
| "reference.dtd"> |
| <reference id="rwsdl" xml:lang="en-us"> |
| <title>Web Services Description Language (WSDL) reference</title> |
| <shortdesc>A WSDL document defines services as collections of network endpoints, |
| or ports. In WSDL, the abstract definition of endpoints and messages is separated |
| from their concrete network deployment or data format bindings. This allows |
| the reuse of abstract definitions: messages, which are abstract descriptions |
| of the data being exchanged, and port types which are abstract collections |
| of operations. </shortdesc> |
| <prolog><metadata> |
| <keywords><indexterm keyref="rwsdl|1|WSDLreference" status="changed">WSDL |
| files<indexterm>reference</indexterm></indexterm><indexterm keyref="rwsdl|2|WebservicesWSDLreference" |
| status="new">Web services<indexterm>WSDL reference</indexterm></indexterm> |
| </keywords> |
| </metadata></prolog> |
| <refbody> |
| <section><p>The concrete protocol and data format specifications for a particular |
| port type constitutes a reusable binding. A port is defined by associating |
| a network address with a reusable binding, and a collection of ports define |
| a service. Hence, a WSDL document uses the following elements in the definition |
| of network services:</p><ul> |
| <li> <uicontrol>Types</uicontrol>: a container for data type definitions using |
| some type system (such as XSD).</li> |
| <li> <uicontrol>Message</uicontrol>: an abstract, typed definition of the |
| data being communicated.</li> |
| <li> <uicontrol>Operation</uicontrol>: an abstract description of an action |
| supported by the service.</li> |
| <li> <uicontrol>Port Type</uicontrol>: an abstract set of operations supported |
| by one or more endpoints.</li> |
| <li> <uicontrol>Binding</uicontrol>: a concrete protocol and data format specification |
| for a particular port type. The binding is usually SOAP and the encoding and |
| data formatting regulations used (also known as the style) is usually literal |
| (this includes document/literal, and sometimes rpc/literal).</li> |
| <li> <uicontrol>Port</uicontrol>: a single endpoint defined as a combination |
| of a binding and a network address.</li> |
| <li> <uicontrol>Service</uicontrol>: a collection of related endpoints.</li> |
| </ul><p>For more information on WSDL, refer to </p><p><xref format="html" |
| href="http://www.w3.org/TR/wsdl" scope="external">www.w3.org/TR/wsdl</xref></p><p>The |
| various WSDL elements can be structured in many ways. It can be in one single |
| WSDL file or in multiple WSDL files.</p></section> |
| </refbody> |
| <related-links> |
| <linklist><title>Related Concepts</title> |
| <link href="../concepts/cws.dita"></link> |
| <link href="../concepts/cwsdl.dita"></link> |
| </linklist> |
| <linklist><title>Related Tasks</title> |
| <link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web |
| services</linktext></link> |
| <link href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita" |
| scope="peer"><linktext> Using the Web Services Explorer</linktext></link> |
| </linklist> |
| </related-links> |
| </reference> |