The answer lies in how SOAP messages are structured, and especially in how extensions are added to the basic SOAP framework.
答案在于SOAP消息的结构，尤其是如何在基本的SOAP框架中添加相应的扩展。
Despite the simplicity of the basic SOAP wrapper, it offers the potential for unlimited extensions by using an optional component called the header.
尽管基本的SOAP包装非常简单，但是通过使用称为Header的可选组件，它提供了不受限制的扩展能力。
I'll start by showing you the structure of the message itself. A basic SOAP message consists of an envelope with two main parts: the header and the body.
一个基本的SOAP消息由包含两个主要部分(报头和主体)的封套组成。
With a basic understanding of SOAP and its purpose, I will now extend the discussion toward its architecture to help you learn the inside story.
有了对SOAP和它的用途的基本理解，我现在就展开对其体系结构的讨论以了解一些深层知识。
Based on the above designed attachments container, the basic functionality of the attachments handler is for two-way conversions between a SOAP message with attachments and an attachments container.
基于上面设计的附件容器，附件处理程序的基本功能是在带有附件的SOAP消息与附件容器之间进行双向转换。
SOAP alone -- SOAP would provide the basic program-to-program "glue" that enables applications to bind together and enter into peer-to-peer communications.
单独使用SOAP?SOAP将提供基本的程序到程序的“粘合剂”，使应用程序能绑定在一起进入对等通信。
In order to follow along with this tutorial, you should have a basic understanding of Simple Object Access Protocol (SOAP) and related technologies, such as WSDL.
为了完成本教程的学习，您应该对简单对象访问协议(SOAP)以及相关的技术(如wsdl)有基本的了解。
In fact, the WS-I has gone so far as to specifically exclude the use of SOAP encoding from their basic interoperability profile.
事实上，WS - I已经到达了这一步，它们明确地将使用SOAP编码排除在它们的基本互操作性概要之外。
This architecture identifies two basic actions a SOAP processor should perform: sending and receiving SOAP messages.
这种体系结构认为SOAP处理器应该两种基本操作：发送和接收 SOAP消息。
A few years ago providing basic XML processing and SOAP 1.1 was enough to claim Service Orientation.
几年前，只要提供基本的XML处理和SOAP 1.1就足以声称是面向服务的。
Most significantly, the WS-I basic profile mandates the use of literal encoding of SOAP request and response messages.
最重要的是，WS- i基本概要文件强制使用SOAP请求和响应消息的文字编码。
Keep in mind that nothing here is specific to SOAP; I'm talking about the basic underpinnings of any RPC system.
记住，这里没有什么是特定于SOAP的；我正在谈论的是任何RPC系统的基本基础。
The note on SOAP submitted to the W3C defines two major items that SOAP contains in addition to its basic XML-RPC features.
提交给W3C的有关SOAP的说明定义了除了基本的XML -RPC特性之外SOAP所包含的两项主要项。
The basic structure of a SOAP message is shown in figure 2.
SOAP消息的基本结构如图2所示。
This article, Part 1 of the series, described what the SOAP nodes are, how to configure them using WSDL, and how to use them in the basic Web service scenarios.
本文是此系列中的第1部分，其中描述了soap节点是什么，如何使用wsdl来配置它们，以及如何在基本的Web服务场景中使用它们。
They use basic XML instead of the complex SOAP XML and are easily consumable
它们使用基本的XML，而不是复杂的SOAP XML，使用非常方便。
The WSS specification also provides a set of basic message-level mechanisms for integrity, confidentiality, and authentication that can help Web service developers secure SOAP exchanges.
WSS规范还提供一系列有助于Web服务开发人员保护soap交换的基本消息级完整性、机密性和身份验证机制。
Of the many ways to call a Web service, the most basic is to manually generate and send SOAP messages.
在调用Web服务的多种方法之中，最基本的方法是手工生成并发送SOAP消息。
The following picture illustrates the basic principles for SOAP request to call caching web services using dynamic cache.
以下图片展示了SOAP请求使用动态缓存调用缓存Web服务的基本原理。
There are two basic fault handlers in Apache SOAP
ApacheSOAP中有两个基本的故障处理程序
Also, a basic understanding of concepts such as Web services and SOAP helps but isn't essential.
另外，对Web服务和SOAP之类的概念有基本的了解也会有所帮助，当并不是必须的。
This wrapper is used internally by the wsrf.js library and includes the basic mechanism for creating the SOAP Envelope and building the requisite XML for the operation.
此包装对象由wsrf . js库内部使用，其中包含了创建SOAP信封和构建操作所必需的XML的基本机制。
The basic architecture that accesses business processes running in WebSphere Process Server from PHP uses SOAP, as shown in Figure 1.
从PHP访问WebSphereProcessServer中运行的业务流程的基本体系结构要使用SOAP，如图1 中所示。
This tutorial series teaches the basic concepts of web services and with different approach of developing web service using different SOAP engines like Apache AXIS2, Apache CXF and JAX-WS.
本系列教程讲述web服务的基本概念，以及使用不同的SOAP引擎(如apacheAXIS2、ApacheCXF和JAX - WS)开发web服务的不同方法。
In addition to basic support for JDK 1.4 (5.1.1), the new WebSphere Studio tooling provides numerous Web services wizards to support document literal and RPC SOAP-encoded services.
除了基本的支持JDK 1.4(5.1.1)，新WebSphereStudio工具提供了大量的Web服务向导，以支持文档文字和RPCSOAP编码服务。
You can use the basic fault handler provided by the Apache SOAP, or create your own.
您可以使用ApacheSOAP提供的基本故障处理程序，或者也可以创建自己的故障处理程序。
JAX-WS, the core platform, USES Tube as a basic processing unit that represents SOAP-level protocol handling code such as MustUnderstand and WS-Addressing processing.
JAX - WS是核心平台，它使用Tube作为基本处理单元，表示SOAP级别的协议处理代码，如MustUnderstand,WS - Addressing处理。
For this discussion, I will assume that you are familiar with basic web service concepts such as SOAP, WSDL, and XML.
对于这里的讨论，我将假定您熟悉基本的Web服务概念(如SOAP、WSDL和XML)。
In its most basic form, you have a SOAP Envelope that contains a SOAP Body, and the Body contains the actual data that is being transmitted.
在其最基本的格式中，有一个包含SOAPBody的SOAPEnvelope，且Body包含了所传递的实际数据。
This tutorial series teaches the basic concepts of web services using different SOAP engines like Apache AXIS2, Apache CXF and JAX-WS.
本系列教程讲述web服务的基本概念，以及使用不同的SOAP引擎（如ApacheAXIS2、 ApacheCXF和 JAX-WS）开发 web 服务的不同方法。
应用推荐