Although SOAP was originally designed to work only with HTTP, any transport protocol or messaging middleware can be used to carry a SOAP message.
虽然SOAP最初在设计上仅与HTTP一起使用，但任何传输协议或消息传递中间件都可用来传送soap消息。
The challenge is that there is not one consistent approach or API to deal with these different mechanisms, and in most real SOA environments, you will come across more than one messaging protocol.
问题是没有一个一致的方法或API来处理这些不同的机制，而且在大多数实际的SOA环境中，您会遇到多个消息传递协议。
Architecturally, components interact via an abstract service model-a messaging model that resides at a level of abstraction above any particular protocol or message-encoding format.
架构上，组件通过一个抽象的服务模型(一个消息传递模型，位于任何特殊协议或消息编码之上的抽象层中)进行交互。
Transport protocol: data services could be consumed via reliable (such as JMS via MQ Series) or unreliable transport messaging protocols (such as HTTP).
传输协议：数据服务可以通过可靠的(如MQSeries上的JMS)或非可靠的(如HTTP)消息传输协议被消费。
This is of particular importance to a class of applications that use XML as a messaging protocol rather than to represent document content, such as Web Services or Instant messaging applications.
对于那些使用XML作为消息传递协议而非表示文档内容的那些应用程序尤其重要，比如Web服务或即时消息应用程序。
For a web service using SOAP messaging protocol, the binding "style" can be either RPC (remote-procedure-call) or document style.
对于使用SOAP消息协议的web服务，绑定的 “样式”可以是RPC（Remote-Procedure-Call，远程程序调用）或文档样式。
For a web service using SOAP messaging protocol, the binding "style" can be either RPC (remote-procedure-call) or document style.
对于使用SOAP消息协议的web服务，绑定的 “样式”可以是RPC（Remote-Procedure-Call，远程程序调用）或文档样式。
应用推荐