没有合适的资源?快使用搜索试试~ 我知道了~
wsdl 文档 pdf格式
4星 · 超过85%的资源 需积分: 10 27 下载量 187 浏览量
2008-10-30
22:08:46
上传
评论 1
收藏 172KB PDF 举报
温馨提示
试读
45页
wsdl 文档wsdl 文档wsdl 文档wsdl 文档wsdl 文档wsdl 文档
资源推荐
资源详情
资源评论
Web Service Definition Language (WSDL)
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):
Erik Christensen, Microsoft
Francisco Curbera, IBM Research
Greg Meredith, Microsoft
Sanjiva Weerawarana, IBM Research
Copyright© 2001 Ariba, International Business Machines Corporation, Microsoft
Abstract
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
Submissions, please see
Acknowledged Submissions to W3C.
This draft represents the current thinking with regard to descriptions of services within Ariba, IBM and Microsoft. It
consolidates concepts found in NASSL, SCL, and SDL (earlier proposals in this space).
This document is a NOTE made available by the W3C for discussion only. Publication of this Note by W3C indicates
no endorsement by W3C or the W3C Team, or any W3C Members. W3C has had no editorial control over the preparation of
http://www.w3.org/TR/wsdl(第 1/45 页)[2008-10-30 21:25:31]
Web Service Definition Language (WSDL)
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.1.1 Document Naming and Linking
2.1.2 Authoring Style
2.1.3 Language Extensibility and Binding
2.1.4 Documentation
2.2 Types
2.3 Messages
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
2.6 Ports
2.7 Services
3 SOAP Binding
3.1 SOAP Examples
3.2 How the SOAP Binding Extends WSDL
3.3 soap:binding
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
4.5 http:operation
4.6 http:urlEncoded
4.7 http:urlReplacement
http://www.w3.org/TR/wsdl(第 2/45 页)[2008-10-30 21:25:31]
Web Service Definition Language (WSDL)
5 MIME Binding
5.1 MIME Binding example
5.2 How the MIME Binding extends WSDL
5.3 mime:content
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
A 3 Location of Extensibility Elements
A 4 Schemas
A 4.1 WSDL Schema
A 4.2 SOAP Binding Schema
A 4.3 HTTP Binding Schema
A 4.4 MIME Binding Schema
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
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:
● Types a container for data type definitions using some type system (such as XSD).
● Message an abstract, typed definition of the data being communicated.
● Operation an abstract description of an action supported by the service.
● Port Typean abstract set of operations supported by one or more endpoints.
● 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
http://www.w3.org/TR/wsdl(第 3/45 页)[2008-10-30 21:25:31]
Web Service Definition Language (WSDL)
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.
In addition to the core service definition framework, this specification introduces specific binding extensions for the
following protocols and message formats:
● SOAP 1.1 (see Section 3)
● HTTP GET / POST (see Section 4)
● MIME (see Section 5)
Although defined within this document, the above language extensions are layered on top of the core
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 4).
Example 1 SOAP 1.1 Request/Response via HTTP
<?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>
http://www.w3.org/TR/wsdl(第 4/45 页)[2008-10-30 21:25:31]
Web Service Definition Language (WSDL)
<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>
1.2 Notational Conventions
1. The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD
NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119
[2].
2. The following namespace prefixes are used throughout this document:
http://www.w3.org/TR/wsdl(第 5/45 页)[2008-10-30 21:25:31]
剩余44页未读,继续阅读
资源评论
- jakung2011-12-04w3c note,版本是wsdl1.1。英文版。
white_eyes
- 粉丝: 22
- 资源: 16
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功