wsdl 文档 pdf格式

Web Services Description Language (WSDL) 1.1

W3C Note 15 March 2001

This version:

http://www.w3.org/TR/2001/NOTE-wsdl-20010315

Latest version:

http://www.w3.org/TR/wsdl

Authors (alphabetically):

WSDL is an XML format for describing network services as a set of endpoints operating on messages containing either

document-oriented or procedure-oriented information. The operations and messages are described abstractly, and then bound to

a concrete network protocol and message format to define an endpoint. Related concrete endpoints are combined into

abstract endpoints (services). WSDL is extensible to allow description of endpoints and their messages regardless of what

message formats or network protocols are used to communicate, however, the only bindings described in this document

describe how to use WSDL in conjunction with SOAP 1.1, HTTP GET/POST, and MIME.

Status

This document is a submission to the World Wide Web Consortium (see Submission Request, W3C Staff Comment) as a

suggestion for describing services for the

W3C XML Activity on XML Protocols. For a full list of all acknowledged

this Note. This document is a work in progress and may be updated, replaced, or rendered obsolete by other documents at any time.

A list of current W3C technical documents can be found at the

Technical Reports page.

Table of Contents

1 Introduction.

1.1 WSDL Document Example

1.2 Notational Conventions

2 Service Definition

2.1 Document Structure

2.3.1 Message Parts

2.3.2 Abstract vs. Concrete Messages

2.4 Port Types

2.4.1 One-way Operation

2.4.2 Request-response Operation.

2.4.3 Solicit-response Operation

2.4.4 Notification Operation

2.4.5 Names of Elements within an Operation

2.4.6 Parameter Order within an Operation

2.5 Bindings

3.4 soap:operation

3.5 soap:body

3.6 soap:fault

3.7 soap:header and soap:headerfault

3.8 soap:address

4 HTTP GET & POST Binding

4.1 HTTP GET/POST Examples

4.2 How the HTTP GET/POST Binding Extends WSDL

4.3 http:address

4.4 http:binding

5 MIME Binding

5.4 mime:multipartRelated

5.5 soap:body

5.6 mime:mimeXml

6 References

A 1 Notes on URIs

A 1.1 XML namespaces & schema locations

A 1.2 Relative URIs

A 1.3 Generating URIs

A 2 Wire format for WSDL examples

A 2.1 Example 1

1. Introduction

As communications protocols and message formats are standardized in the web community, it becomes increasingly possible

and important to be able to describe the communications in some structured way. WSDL addresses this need by defining an

XML grammar for describing network services as collections of communication endpoints capable of exchanging messages.

WSDL service definitions provide documentation for distributed systems and serve as a recipe for automating the details involved

in applications communication.

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. The concrete protocol and data format specifications for a particular port type constitutes

● Binding a concrete protocol and data format specification for a particular port type.

● Port a single endpoint defined as a combination of a binding and a network address.

● Service a collection of related endpoints.

These elements are described in detail in Section 2. It is important to observe that WSDL does not introduce a new type

definition language. WSDL recognizes the need for rich type systems for describing message formats, and supports the

XML Schemas specification (XSD)

[11] as its canonical type system. However, since it is unreasonable to expect a single type

system grammar to be used to describe all message formats present and future, WSDL allows using other type definition languages

via extensibility.

In addition, WSDL defines a common binding mechanism. This is used to attach a specific protocol or data format or structure to

an abstract message, operation, or endpoint. It allows the reuse of abstract definitions.

service definition

framework. Nothing precludes the use of other binding extensions with WSDL.

1.2 WSDL Document Example

The following example shows the WSDL definition of a simple service providing stock quotes. The service supports a

single operation called GetLastTradePrice, which is deployed using the SOAP 1.1 protocol over HTTP. The request takes a

ticker symbol of type string, and returns the price as a float. A detailed description of the elements used in this definition can

be found in Section 2 (core language) and Section 3 (SOAP binding).

This example uses a fixed XML format instead of the SOAP encoding (for an example using the SOAP encoding, see

Example 1 SOAP 1.1 Request/Response via HTTP