The WS-SecurityPolicy 1.3 schema just extends the 1.2 version, adding a few more elements.
WS-SecurityPolicy 1.3模式是 1.2版本的扩展，增加了一些新的元素。
The complete set of token assertion classes is described in the WS-SecurityPolicy specification.
WS-SecurityPolicy规范中描述了标记声明类的完整集合。
Both Axis2 and Metro use custom WS-SecurityPolicy extensions to provide security parameters of this type.
Axis2和Metro使用定制的WS - SecurityPolicy扩展提供这种安全参数。
Part of this information is handled as configuration data, embedded in the WS-SecurityPolicy document for the service.
这些信息中的一部分被作为配置数据处理，被嵌入到服务的WS - SecurityPolicy文档中。
To make use of the WS-SecurityPolicy configuration on the client, you do need to take some action in your client code.
要在客户机中利用WS-SecurityPolicy配置，您一定需要在客户机代码中采取一些操作。
You've seen this in past articles of this series, where many of the WS-SecurityPolicy assertions contain nested policy expressions.
在本系列之前的文章中，您可能见过WS - SecurityPolicy断言包含嵌套的策略表达式。
Tools can, in turn, generate necessary machine-level details (such as a WS-SecurityPolicy expression), as illustrated in Listing 2.
工具则可进而生成必要的机器级详细信息(如ws - SecurityPolicy表达式)，如清单2所示。
WS-SecurityPolicy security configurations detail the security processing needed for messages being exchanged between a client and service.
WS - SecurityPolicy安全配置指定在客户机和服务之间交换的消息所需的安全处理。
Similar to these other stacks, CXF uses WS-SecurityPolicy to configure WS-Security handling (though manual configuration is also possible).
与这些堆栈一样，CXF 也使用WS-SecurityPolicy配置WS-Security 安全处理（也可以手工配置）。
For instance, a WS-SecurityPolicy may require the client to sign request messages sent to the server, providing nonrepudiation for the service.
例如，WS - SecurityPolicy可能要求客户机对发送到服务器的请求消息进行签名，这为服务提供不可否认性。
WS-SecurityPolicy specifies the message-grouping levels at which certain types of policy assertions should be attached to a service description.
WS - SecurityPolicy指定了消息分组级别，其中特定类型的策略断言会被附加到一个服务描述中。
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本身。
WS-SecurityPolicy assertions not listed above are nested within other assertions, so the placement of the containing assertion controls their level.
上面未列出的WS - SecurityPolicy断言是嵌在其他断言中的，所以所包含的断言位置决定了它们的级别。
Unfortunately, the implementations of WS-Policy and WS-SecurityPolicy processing used by web services stacks don't implement much of the flexibility.
不幸的是，web服务栈使用的WS-Policy和WS-SecurityPolicy处理的实施不能实现较大的灵活性。
Beyond these common components, however, the stacks differ in many ways, including their processing engines and WS-SecurityPolicy configuration handling.
但是，除了这些公共组件之外，各栈之间的差异还包括它们的处理引擎和WS - SecurityPolicy配置处理。
In the first part of this article, you'll learn why WS-SecurityPolicy can be difficult to work with and see the causes of common WS-SecurityPolicy errors.
在本文的第一部分，您将了解到为什么WS - SecurityPolicy很难使用，并且会了解一些常见的WS - SecurityPolicy错误的发生原因。
Almost all of the rest are defined as allowing both extension attributes and elements from other namespaces, but not from the WS-SecurityPolicy namespace.
而其他元素则同时支持扩展属性和其他名称空间的元素，但是不支持WS - SecurityPolicy名称空间的元素。
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断言时经常遇到的问题。
In earlier articles, you saw this done for a complete WS-SecurityPolicy configuration, including the Rampart configuration, and applied to the service as a whole.
在早期文章中我们执行了这个操作，以获得包括Rampart配置的完整WS - SecurityPolicy配置，并作为一个整体应用到服务。
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的标准化已经很多年了，但是这些技术的早期版本在标准发布之前已经被广泛应用了。
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只需要增加少量工作就能够干净利落完成数据处理。
This approach works and can be useful in testing, but for production use WS-SecurityPolicy is best associated directly with a service definition by being embedded within a WSDL document.
这个方法可以奏效，并且可用于测试，但是对于生产应用来说，最好通过将WS - SecurityPolicy内嵌到WSDL文档将其直接关联到服务定义。
For instance, if you were to move the element (near the end of Listing 1) inside the preceding element's Policy, you'd have a structure that doesn't match the WS-SecurityPolicy standard.
例如，如果您将元素(清单1末尾)移动到上述元素的Policy内部时，您就得到一个不符合WS - SecurityPolicy标准的结构。
Listing 8 shows a pair of the namespace version-specific bindings referenced by elements in the Listing 7 binding, one for a WS-Policy namespace and one for a WS-SecurityPolicy namespace.
清单8显示了清单7绑定中元素所引用的一对与名称空间版本相关的绑定，其中一个是WS -Policy名称空间，另一个是WS - SecurityPolicy名称空间。
Listing 8 shows a pair of the namespace version-specific bindings referenced by elements in the Listing 7 binding, one for a WS-Policy namespace and one for a WS-SecurityPolicy namespace.
清单8显示了清单7绑定中元素所引用的一对与名称空间版本相关的绑定，其中一个是WS -Policy名称空间，另一个是WS - SecurityPolicy名称空间。
应用推荐