Fat people just use more soap!
肥胖的人只是多使用香皂！
More and more soap operas are widely received.
越来越多的肥皂剧收到观众欢迎。
All things being equal, fat people use more soap.
所有事物平等，胖人用更多的香皂。
And these revisions will lead to additional changes in SOAP implementations, which of course means more upgrades to your development environment.
这些修订版会导致SOAP实现的额外变更，这当然意味着对您的开发环境进行更多升级。
This can be very convenient, but note that the SOAP domain tree in general gives you more flexibility and control.
这可能非常便利，但是请注意，soap域树通常为您提供了更多的灵活性和控制。
While these patterns are at the abstract level of WSDL, "binding" to SOAP provides for more variability in integration mechanism by means of having the operation as RPC-oriented or document-oriented.
这些模式处于WSDL抽象级别，而到SOAP的“绑定”可通过将操作指定为面向RPC或面向文档的操作而在集成机制方面提供更多的变化。
A real life solution would build the new SOAP message in a more generic fashion, reading the values for things like target namespace, operation, port name, and so on, from context properties.
实际的解决方案将以一种更通用的方式构建新SOAP消息，以便从上下文属性中读取诸如目标名称空间、操作、端口名称等的值。
They may be implemented by one or more handlers in any given SOAP stack.
在一个给定的SOAP协议栈中，二者都可以有一个或多个处理器。
Usually your ESQL USES at least two namespaces: the namespace for the SOAP envelope and one or more namespaces used by your application data.
ESQL通常至少使用两个命名空间：SOAP信封的命名空间和应用程序数据使用的一个或多个命名空间。
In the next section, we'll see how a SOAP wrapper not only makes this easier but also more intuitive and safer.
在下一节中，我们将介绍SOAP封装程序是如何对此进行简化，并以更加直观和更加安全的方式表现它们。
WSDL may define a SOAP binding for a service, but it also defines a more abstract description of the service at a level above the SOAP messaging layer.
WSDL可以定义为将SOAP绑定到服务上，但是也可以在高于SOAP消息的层次上定义一种更加抽象的描述。
But there is certainly more to SOAP than just messaging, and I'll now show how clients interact with SOAP, and how they interact with RMI.
当然，SOAP不仅仅是消息传递还有更多，现在，我将演示客户机如何与SOAP交互，以及如何与rmi交互。
When you learn about more advanced features later in this book, you'll look at SOAP messages in more detail and consider some of the options you can set to control how SOAP messages are built.
当您在本书后面部分学习了更多高级特性之后，您会更详细地了解SOAP消息，并考虑一些您能设置用来控制如何构建SOAP消息的选项。
The semantics of these APIs is geared more toward technical aspects of services invocations and SOAP processing, then toward service usage and support.
这些API的语义更偏向服务调用的技术方面和SOAP处理过程，其次才是服务的使用和支持。
You will now tweak the SOAP message by renaming these element names to make it more meaningful.
现在，您可以调整SOAP消息，通过重新命名这些元素名称使这些名称变得更有意义。
The above SOAP payload now looks more meaningful.
上述SOAP有效负载现在看起来更有意义。
Since there are more tools, XML makes SOAP more accessible than other RPC standards.
因为有更多的工具，XML使soap比其他RPC标准更容易访问。
Also, and this is an important point, it's very possible that the task for which you've chosen to use SOAP could be accomplished more easily using XML-RPC.
同样，并且这是很重要的一点，使用XML -RPC完成任务要比您选择使用SOAP更容易，这是很有可能的。
But if you're creating a new message flow and using WSDL, then the SOAP nodes offer a more complete solution.
但是，如果您在创建新的消息流并使用WSDL，则soap节点可以提供更完整的解决方案。
If it's more transactional in nature, if it's more guarded in nature, its more business critical, oftentimes, the information is coming across SOAP interfaces.
如果交互本身就更加事务性，更谨慎，更业务敏感的功能，那么通常使用SOAP接口来进行交互。
AXIS is essentially a SOAP engine; it's more like a framework for constructing SOAP processors such as clients, servers, and gateways.
AXIS实质上是一个SOAP引擎；它更像是一个框架，例如构造客户端、服务器、网关的SOAP处理器。
First is the support for REST-style programming, which is a bit more developer-friendly than SOAP.
第一类是对REST风格编程的支持，这种风格对开发人员来说比SOAP更加友好。
Because both the public and private components in the ISV's integration gateway are based on J2EE technologies, use of JMS and RMI is highly appropriate and much more efficient than SOAP and HTTP.
因为ISV的集成网关中的公共组件和私有组件都是基于J2EE技术的，所以使用JMS和RMI是非常合适的，而且比SOAP和HTTP效率高得多。
For instance, we could have used SOAP over JMS, allowing for a more scalable asynchronous connection than that available with SOAP over HTTP.
例如，我们可以使用通过JMS的SOAP，以实现比通过HTTP的SOAP的异步连接的可伸缩性更好的异步连接。
Determine the set of roles in which the current SOAP node is acting (more on this below).
决定当前的SOAP节点正在扮演的角色集(下面有更多的关于这方面的内容的介绍)。
That said, I think that rest is just as, or even more restrictive than SOAP is.
也就是说，我认为REST就像SOAP一样受限制，或者更甚。
This is more akin to a document-style SOAP message than an RPC-style message.
这更类似于文档样式的SOAP消息而不是rpc样式的消息。
However, the SOAP data model is more general and can deal with graphs rather than just trees.
但是，SOAP数据模型更通用，可以处理图而不仅仅是树。
In addition, XML-RPC libraries are much more mature than SOAP libraries.
除此以外，XML - rpc库要比soap库成熟得多。
The third generation of Web services requires faster, and more robust, SOAP engines -- and the existing Axis is not enough for this.
第三代Web服务要求使用更快、更可靠的SOAP引擎——现有的Axis已不足以满足此要求。
应用推荐