From Figure 4, it is clear that atomic transactions using web services (WS-C, and WS-AT) are substantially the same as without web services (Figures 2 and 3, for example).
从图4中可以清楚地得到使用Web服务的原子事务(WS - c和ws - AT)和不使用Web服务的原子事务(例如图2和3)大体上是相同的。
Before you go any further into this article, you should have a basic understanding of the BPEL, WS-C, and WS-T specifications, as many of the concepts from these specifications will be explored here.
在进一步学习本文之前，您应该对BPEL、WS - c和ws - T规范有一个基本的理解，因为我们将在这里探讨来自这些规范的许多概念。
The best practice is to use WS-AT within a single enterprise, avoiding WS-AT usage across enterprise domains.
最佳做法是在单一的企业中使用WS -AT，从而避免跨企业域的WS - AT使用。
You'll learn the configuration steps and best practices involved in setting up a clustered topology to which you can deploy and configure a JAX-WS application to receive WS-RM messages.
您将了解设置集群拓扑涉及的配置步骤和最佳实践，您可以为该集群拓扑部署和配置JAX - WS应用程序来接收WS - RM消息。
This article will outline how the BPEL, WS-C, and WS-T specifications simplify support for asynchronous operations.
本文将概述一下BPEL、WS-C和WS-T规范如何简化对异步操作的支持。
The next article in the series takes this topic further, looking at the problems frequently encountered in writing WS-Policy and WS-SecurityPolicy assertions.
本系列的下一篇文章会进一步讨论这个话题，讨论编写WS - Policy和WS - SecurityPolicy断言时经常遇到的问题。
Though not shown in this article, this use of secret keys is essentially the same as the signing example for WS-SecureConversation discussed in "WS-SecureConversation performance."
虽然本文没有介绍，但是保密密钥的使用方法本质上与“WS -SecureConversation性能”中讨论的WS - SecureConversation签名例子是一样的。
The loose structure of WS-Policy and WS-SecurityPolicy also causes problems for data binding, but here again JiBX can cleanly handle the data with a little added effort.
WS - Policy和WS -SecurityPolicy的宽松结构也会给数据绑定带来问题，但是同样，JiBX只需要增加少量工作就能够干净利落完成数据处理。
In all these scenarios, you can use the higher-level Web service protocols such as WS-Addressing and WS-Security, which give you flexible routing schemes and secure interactions, respectively.
在所有这些场景中，您可以使用诸如ws - Addressing和WS - Security等高级Web服务协议，这些协议分别为您提供灵活的路由方案和安全的交互。
The standardization of both WS-Policy and WS-SecurityPolicy took years, and earlier versions of the technologies became widely used before the standards were released.
WS -Policy和WS -SecurityPolicy的标准化已经很多年了，但是这些技术的早期版本在标准发布之前已经被广泛应用了。
WS-BusinessActivity (WS-BA), which addresses coordination of long-running activities and supports the concept of compensation.
WS -BusinessActivity (WS -BA)可以解决长时间运行活动的协作问题并支持补偿概念。
In this article, you'll see how you can go a step further and break free of the need for client certificates in both plain WS-Security and WS-SecureConversation exchanges.
在本文中，您将会了解您可以如何更一步地打破在普通的WS - Security和WS -SecureConversation交换方面都需要客户端证书的现状。
A WS-Addressing Endpoint Reference or a WS-Transaction Coordination Context could have easily contained the correlation ID and refresh timer values.
WS -Addressing终点参考和WS -Transaction协调上下文可以很容易地集成到相关ID和刷新时间值的实现中。
By using Web services standards, such as WS-ReliableMessaging and WS-Security, you can use Synapse to enable secure, reliable connections between applications.
通过使用Web服务标准，如WS - ReliableMessaging和WS - Security，您可以使用Synapse以确保应用程序之间安全的、可靠的连接。
The framework introduced by BPEL, WS-Coordination, and WS-Transaction provides support for a broad spectrum of transactional and non-transaction business processes.
WS-Coordination和WS-Transaction引入的框架为种类繁多的事务性和非事务性业务流程提供了支持。
By extending on this base, BPEL, WS-Coordination, and WS-Transaction help business streamline the integration process and implement more flexible business processes.
在这个基础上加以扩展，BPEL、WS - Coordination和WS - Transaction可以帮助企业更有效地集成流程并实现更灵活的业务流程。
The gateway model can include applying authentication and authorization to incoming messages using the Apache Rampart framework to support WS-Security and WS-SecureConversation.
网关模型可以包括使用ApacheRampart框架应用身份验证机制、以及对进入的消息进行授权，以支持WS - Security和WS - SecureConversation。
To illustrate the function and benefits of the BPEL, WS-Transaction, and WS-Coordination specifications, we will explore the application of those technologies to a real-world business scenario.
为了说明BPEL、WS - Transaction和WS - Coordination规范的功能和优点，我们将研究这些技术在真实的业务模式中的应用。
To define the actual assertions that make up a policy, you use domain-specific extensions such as WS-SecurityPolicy, rather than WS-Policy per se.
为了定义构成策略的真实断言，您需要使用特定扩展，比如WS - SecurityPolicy，而不是WS - Policy本身。
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文档的能力。
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-Policy integration: Axis2 fully supports WS-Policy, which is integrated into the core of the engine.
WS -Policy集成：axis2完全支持WS - Policy，该规范已集成到了引擎的核心中。
They combine message transport and SOAP semantics to support a consistent SOAP domain logical tree format and the next-generation Web services standards WS-Security and WS-Addressing.
soap节点组合了消息传输和soap语义，以支持一致的soap域逻辑树格式和下一代Web服务标准WS - Security和WS - Addressing。
Protocol channels support implementation of many web services standards, for example WS-Security and WS-Reliability over the basic transport channels.
协议管道支持多种webservices标准的实现，例如建立在基础传输管道上的WS-Security和WS-Reliability。
WS-Policy and WS-Trust, have also become standards in W3C / OASIS respectively and are common features in web services security environments.
WS-Policy和WS-Trust也已经分别成为W3C /OASIS 中的标准，它们是Web服务安全环境中的公共特性。
WS-Coordination (WS-Coor), which provides the underlying mechanism for the creation and exchange of transaction context.
WS - Coordination (WS - Coor)提供创建和交换事务上下文的基础机制。
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标准之上构建的一种标准，用于支持涉及多个消息的安全交换。
The properties were name-value pairs that could be accessed using the operations defined by the WS-ResourceProperties (WS-RP) specification.
属性是名称-值对，可以使用由WS -ResourceProperties (WS- RP)规范定义的操作来访问。
Distributed security monitoring Web services should include the coupling switch mechanism plus the WS-Resource Framework WS-Resource Transfer.
分布式安全监视Web服务应该包括耦合切换机制以及WS -ResourceFramework和WS - ResourceTransfer。
It implements WS-Federation and WS-Trust protocols and can handle SAML 1.1 and 2.0 security tokens.
WIF实现了WS -Federation和WS -Trust协议，能够处理SAML1.1和2.0的安全令牌。
应用推荐