blocks|key|172554|text|WSDL+(Web服务定义语言)是描述web服务的元数据文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|172555|例如操作名称、参数等。|172556|soap消息是实际的有效负载|172557|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

A WSDL (Web Service Definition Language) is a meta-data file that describes the web service.

Things like operation name, parameters etc.

The soap messages are the actual payloads

blocks|key|390668|text|每个请求都会发送一个SOAP文档。假设我们是一家书店，有一个远程服务器，我们查询它来了解某本书的当前价格。假设我们需要将图书的标题、页数和ISBN号传递给服务器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|390669|每当我们想知道价格时，我们都会发送一个独特的SOAP消息。它看起来像这样；|390670|<SOAP-ENV:Envelope
++xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
++SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
++<SOAP-ENV:Body>
++++<m:GetBookPrice+xmlns:m="http://namespaces.my-example-book-info.com">
++++++<ISBN>978-0451524935</ISBN>
++++++<Title>1984</Title>
++++++<NumPages>328</NumPages>
++++</m:GetBookPrice>
++</SOAP-ENV:Body>
</SOAP-ENV:Envelope>+|code-block|syntax|javascript|390671|我们希望得到一个SOAP响应消息，比如；|390672|<SOAP-ENV:Envelope
++xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
++SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
++<SOAP-ENV:Body>
++++<m:GetBookPriceResponse+xmlns:m="http://namespaces.my-example-book-info.com">
++++++<CurrentPrice>8.99</CurrentPrice>
++++++<Currency>USD</Currency>
++++</m:GetBookPriceResponse>
++</SOAP-ENV:Body>
</SOAP-ENV:Envelope>|390673|然后，WSDL描述了在服务器接收到消息时如何处理/处理该消息。在我们的例子中，它描述了标题、NumPages和ISBN的类型，我们是否应该期待来自GetBookPrice消息的响应，以及响应应该是什么样子。|390674|类型看起来像这样；|390675|<wsdl:types>

++
++<xsd:schema+targetNamespace="http://namespaces.my-example-book-info.com"
++++xmlns:xsd="http://www.w3.org/1999/XMLSchema">

++++<xsd:element+name="GetBookPrice">
++++++<xsd:complexType>
++++++++<xsd:sequence>
++++++++++<xsd:element+name="ISBN"+type="string"/>
++++++++++<xsd:element+name="Title"+type="string"/>
++++++++++<xsd:element+name="NumPages"+type="integer"/>
++++++++</xsd:sequence>
++++++</xsd:complexType>
++++</xsd:element>

++++<xsd:element+name="GetBookPriceResponse">
++++++<xsd:complexType>
++++++++<xsd:sequence>
++++++++++<xsd:element+name="CurrentPrice"+type="decimal"+/>
++++++++++<xsd:element+name="Currency"+type="string"+/>
++++++++</xsd:sequence>
++++++</xsd:complexType>
++++</xsd:element>

++</xsd:schema>
</wsdl:types>|390676|但是WSDL也包含更多的信息，关于哪些函数链接在一起进行操作，哪些操作在服务中可用，以及您可以访问服务/操作的网络位置。|390677|另请参阅W3+Annotated+WSDL+Examples|offset|length|390678|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3.org/2001/03/14-annotated-WSDL-examples.html^0|0|0|0|0|0|0|0|0|0|4|Q|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|19|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|1A|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|R|5|F|7|1D|8|@]|9|@]|A|$G|H]]|$1|S|3|T|5|6|7|1E|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1F|8|@]|9|@$W|1G|X|1H|1|1I]]|A|$]]|$1|Y|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

A SOAP document is sent per request. Say we were a book store, and had a remote server we queried to learn the current price of a particular book. Say we needed to pass the Book's title, number of pages and ISBN number to the server.

Whenever we wanted to know the price, we'd send a unique SOAP message. It'd look something like this; 

<pre><code>&lt;SOAP-ENV:Envelope
 xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
 SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"&gt;
 &lt;SOAP-ENV:Body&gt;
 &lt;m:GetBookPrice xmlns:m="http://namespaces.my-example-book-info.com"&gt;
 &lt;ISBN&gt;978-0451524935&lt;/ISBN&gt;
 &lt;Title&gt;1984&lt;/Title&gt;
 &lt;NumPages&gt;328&lt;/NumPages&gt;
 &lt;/m:GetBookPrice&gt;
 &lt;/SOAP-ENV:Body&gt;
&lt;/SOAP-ENV:Envelope&gt; 
</code></pre>

And we expect to get a SOAP response message back like;

<pre><code>&lt;SOAP-ENV:Envelope
 xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
 SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"&gt;
 &lt;SOAP-ENV:Body&gt;
 &lt;m:GetBookPriceResponse xmlns:m="http://namespaces.my-example-book-info.com"&gt;
 &lt;CurrentPrice&gt;8.99&lt;/CurrentPrice&gt;
 &lt;Currency&gt;USD&lt;/Currency&gt;
 &lt;/m:GetBookPriceResponse&gt;
 &lt;/SOAP-ENV:Body&gt;
&lt;/SOAP-ENV:Envelope&gt;
</code></pre>

The WSDL then describes how to handle/process this message when a server receives it. In our case, it describes what types the Title, NumPages &amp; ISBN would be, whether we should expect a response from the GetBookPrice message and what that response should look like. 

The types would look like this; 

<pre><code>&lt;wsdl:types&gt;

 &lt;!-- all type declarations are in a chunk of xsd --&gt;
 &lt;xsd:schema targetNamespace="http://namespaces.my-example-book-info.com"
 xmlns:xsd="http://www.w3.org/1999/XMLSchema"&gt;

 &lt;xsd:element name="GetBookPrice"&gt;
 &lt;xsd:complexType&gt;
 &lt;xsd:sequence&gt;
 &lt;xsd:element name="ISBN" type="string"/&gt;
 &lt;xsd:element name="Title" type="string"/&gt;
 &lt;xsd:element name="NumPages" type="integer"/&gt;
 &lt;/xsd:sequence&gt;
 &lt;/xsd:complexType&gt;
 &lt;/xsd:element&gt;

 &lt;xsd:element name="GetBookPriceResponse"&gt;
 &lt;xsd:complexType&gt;
 &lt;xsd:sequence&gt;
 &lt;xsd:element name="CurrentPrice" type="decimal" /&gt;
 &lt;xsd:element name="Currency" type="string" /&gt;
 &lt;/xsd:sequence&gt;
 &lt;/xsd:complexType&gt;
 &lt;/xsd:element&gt;

 &lt;/xsd:schema&gt;
&lt;/wsdl:types&gt;
</code></pre>

But the WSDL also contains more information, about which functions link together to make operations, and what operations are avaliable in the service, and whereabouts on a network you can access the service/operations.

See also <a href="http://www.w3.org/2001/03/14-annotated-WSDL-examples.html" rel="noreferrer">W3 Annotated WSDL Examples</a>

blocks|key|390726|text|我们可以考虑一个电话，号码是wsdl，信息交换是soap。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|390727|WSDL描述了如何与通信server.SOAP进行连接，并提供了通信消息。|390728|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

We can consider a telephone call In that Number is wsdl and exchange of information is soap.

WSDL is description how to connect with communication server.SOAP is have communication messages.

blocks|key|390746|text|简单地说，如果你有一个计算器的web服务。WSDL告诉您可以实现或公开给客户端的函数。例如:添加、删除、减去等。使用SOAP时，您实际执行的操作包括doDelete()、doSubtract()、doAdd()。所以SOAP和WSDL是苹果和橙子。我们不应该比较它们。它们都有各自不同的功能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|390747|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In a simple terms if you have a web service of calculator. WSDL tells about the functions that you can implement or exposed to the client. For example: add, delete, subtract and so on. Where as using SOAP you actually perform actions like doDelete(), doSubtract(), doAdd(). So SOAP and WSDL are apples and oranges. We should not compare them. They both have their own different functionality.

blocks|key|390763|text|SOAP+:它是一种基于XML的开放标准通信协议，用于从用户到web服务交换信息，反之亦然。soap就是以某种方式组织数据的文档。对于每个请求和响应，可能存在单独的soap。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|390764|WSDL:在soap中，数据是以某种方式组织的，这种组织是在WSDL中指定的，必须使用的数据类型也在这里指定。对于请求和响应，将提供单个WSDL|390765|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

SOAP :
 It's an open standard XML based Communication protocol which is used to exchange information from the user to web service or vice versa.
 The soap is just the document in which the data are organized in some Manner.
 For every request and response separate soap may be present.

WSDL:
 In soap the data are organized in some manner and this organization is specified in WSDL, The data type which has to be used are also specified here.
 For request and response single WSDL will be present

blocks|key|172753|text|比电话更好的类比:从邮购服务中通过邮寄订购产品。WSDL文档类似于说明如何创建服务提供者将接受的订单类型的说明。SOAP消息就像一个带有标准设计(大小、形状、结构)的信封，世界各地的邮局都知道如何处理。你把你的订单放进这样一个信封里。网络(例如互联网)就是邮政服务。你把你的信封放进邮件里。邮政服务的员工不会看信封里的东西。有效负载XML是您封装在信封中的定单。邮局投递信封后，web服务提供商打开信封并处理订单。如果您正确创建并填写了表单，他们会将您订购的产品邮寄回给您。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|172754|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Better analogy than the telephone call: Ordering products via postal mail from a mail-order service.
The WSDL document is like the instructions that explain how to create the kind of order forms that the service provider will accept.
A SOAP message is like an envelope with a standard design (size, shape, construction) that every post office around the world knows how to handle. You put your order form into such an envelope. The network (e.g. the internet) is the postal service. You put your envelope into the mail. The employees of the postal service do not look inside the envelope.
The payload XML is the order form that you have enclosed in the envelope. After the post office delivers the envelope, the web service provider opens the envelope and processes the order form. If you have created and filled out the form correctly, they will mail the product that you ordered back to you.

blocks|key|390799|text|WSDL是API提供者和客户端之间的一种约定，它描述了web服务:公共函数、可选/必填字段……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|390800|但是soap消息是在客户端和提供者(有效负载)之间传输的数据|390801|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The WSDL is a kind of contract between API provider and the client it's describe the web service : the public function , optional/required field ... 

But The soap message is a data transferred between client and provider (payload)

I am confused about how SOAP messages and WSDL fit together? I have started looking into SOAP messages such as:

<pre><code> POST /InStock HTTP/1.1
Host: www.example.org
Content-Type: application/soap+xml; charset=utf-8
Content-Length: nnn

&lt;?xml version="1.0"?&gt;
&lt;soap:Envelope
xmlns:soap="http://www.w3.org/2001/12/soap-envelope"
soap:encodingStyle="http://www.w3.org/2001/12/soap-encoding"&gt;

&lt;soap:Body xmlns:m="http://www.example.org/stock"&gt;
 &lt;m:GetStockPrice&gt;
 &lt;m:StockName&gt;IBM&lt;/m:StockName&gt;
 &lt;/m:GetStockPrice&gt;
&lt;/soap:Body&gt;

&lt;/soap:Envelope&gt;
</code></pre>

Are all SOAP messages WSDL's? Is SOAP a protocol that accepts its own 'SOAP messages' or 'WSDL's? If they are different, then when should I use SOAP messages and when should I use WSDL's?

Some clarification around this would be awesome.

Difference between a SOAP message and a WSDL?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我搞不懂SOAP消息和WSDL是如何结合在一起的？我已经开始研究SOAP消息，例如： POST /InStock HTTP/1.1Host: www.example.orgContent-Type: application/soap+xml; charset=utf-8Content-Length: nnn<?x...

问SOAP消息和WSDL之间的区别？
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SOAP消息和WSDL之间的区别？EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SOAP消息和WSDL之间的区别？
EN