New WS-BPEL constructs are supported.
支持新的WS - BPEL构造。
WS-Trust combines two related functions.
WS - Trust综合了两个相关函数。
You may see some WS-I compliance warnings.
您可能会遇到一些WS - i遵从性警告。
Later on I'll talk about how WS-R differs.
稍后我将讨论WS - R的不同点。
How are event handlers specified in WS-BPEL?
如何在WS - BPEL中指定事件处理程序？
WS-AT is operating system and platform neutral.
WS - AT与操作系统和平台无关。
WS-BPEL supports importing two types of documents.
WS - BPEL支持导入两种文档。
WS-I has refined the standard to ensure interoperability.
为确保互操作性，WS - i已细化了该标准。
Security is one of the areas WS-I has covered in profiles.
在配置文件中安全性是WS - i所涉及的领域之一。
This is where WS-RM will store messages and sequence state.
这是WS - RM存储消息和序列状态的地方。
A traditional WS-BPEL process handles this class of processes.
传统的WS -BPEL流程就处理此类流程。
You may see some WS-I compliance warnings, which you can ignore.
您可能会遇到一些WS - i遵从性警告，您可以忽略它们。
WS-BPEL defines several restrictions that apply to event handlers.
WS - BPEL定义了若干应用到事件处理程序的限制。
WS-POS holds potential benefits for all members of the retail ecosystem.
WS -POS对零售生态系统中的所有成员都具有潜在的优点。
WS-BPEL imposes an additional restriction to request-response operations.
WS - BPEL对请求-响应操作施加了其他限制。
WS-BPEL specifies another construct to deal with external events: the event handler.
WS - BPEL指定了另一个构造来处理外部事件：事件处理程序。
In order to indicate support for WS-Eventing, two WS-Policy assertions are specified.
为了表明对WS - Eventing的支持，指定了两个WS - Policy断言。
Most people will probably not directly use the various features defined in WS-C and WS-AT.
大多数人可能不会直接使用定义在Web服务协调和Web服务原子事务中的各种功能。
WS-Policy integration: Axis2 fully supports WS-Policy, which is integrated into the core of the engine.
WS -Policy集成：axis2完全支持WS - Policy，该规范已集成到了引擎的核心中。
WS-Routing describes the SOAP message initiator, where the message starts, as the initial WS-Routing sender.
WS -Routing将SOAP消息发起者(消息开始的地方)描述为初始ws - Routing发送方。
The best practice is to use WS-AT within a single enterprise, avoiding WS-AT usage across enterprise domains.
最佳做法是在单一的企业中使用WS -AT，从而避免跨企业域的WS - AT使用。
The initial WS-Routing sender must generate a WS-Routing path header to indicate the WS-Routing message path.
初始ws -Routing发送方必须生成一个WS - Routingpath头以指出WS - Routing消息路径。
This article will outline how the BPEL, WS-C, and WS-T specifications simplify support for asynchronous operations.
本文将概述一下BPEL、WS-C和WS-T规范如何简化对异步操作的支持。
WS-Routing defines a certain set of rules to describe the message path from the WS-Routing sender to the WS-Routing receiver.
WS -Routing定义了一组确定的规则来描述从WS - Routing发送方到WS - Routing接收方的消息路径。
Notice this is not that different from how WS-RM uses empty response flows to send new SOAP envelopes to carry WS-RM acknowledgements.
请注意，这与现在 WS-RM使用空响应流发送包含 WS-RM确认信息的新SOAP信封的方式区别并不大。
The WS-Routing header entry indicates the ultimate WS-Routing receiver and zero or more WS-Routing intermediaries in the forward message path.
WS -Routing头条目指出了正向消息路径中的最终WS - Routing接收方以及零个或更多的WS - Routing中介体。
WS-SecureConversation is a standard that builds on the WS-Security and WS-Trust standards to support secure exchanges involving multiple messages.
WS - SecureConversation是在WS - Security和WS -Trust标准之上构建的一种标准，用于支持涉及多个消息的安全交换。
One important feature of the WS-Inspection specification, is the ability to link a WS-Inspection document to one or more different WS-Inspection documents.
WS -Inspection规范的一个重要功能是具有将一个WS - Inspection文档链接到一个或多个不同ws - Inspection文档的能力。
WS(西萨摩亚)8.3%。
应用推荐