The BPEL4WS demo is available on our server.
可以在开发者服务器上找到BPEL4WS演示
BPEL4WS supports two distinct usage scenarios.
BPEL4WS支持两种截然不同的使用情形。
Luckily, BPEL4WS provides the necessary changes.
很幸运，BPEL4WS提供了必要的改变。
BPEL4WS USES service link types to define partners.
BPEL4WS用服务链接类型来定义伙伴。
There are two types of processes defined in BPEL4WS
在 BPEL4WS中定义了两种类型的流程
That language in the Web services world is the BPEL4WS.
在Web服务的世界中，这种语言就是BPEL4WS。
Marketplace demo code is available in the BPEL4WS tutorial.
市场演示代码（ bpel4ws_demo.zip）。
Behavioral descriptions, such as a BPEL4WS abstract process.
行为描述，例如BPEL4WS抽象流程。
Table 1 provides a summary of the BPEL4WS Process components.
表1提供了对BPEL4WS流程(BPEL4WS Process)的组件的总结。
In this section, I will briefly describe some components of BPEL4WS.
在这一部分，我将简单地描述BPEL4WS的一些组件。
A BPEL4WS process is defined in terms of its interactions with partners.
使用合作伙伴的交互方式，定义了该BPEL4WS流程。
In this article we briefly explained the main underlying concepts of BPEL4WS.
我们在本文简要地解释了BPEL4WS主要的底层概念。
BPEL4WS has exceptions (faults) built into the language via the and constructs.
BPEL4WS通过和构造在语言中内置了异常(故障)。
With BPEL4WS, Web services get this necessary boost which enables peer dialogues.
通过BPEL4WS,Web服务可以得到进行对等体对话的必要增强功能。
BPEL4WS provides a collection of basic and structured activities to use in a process.
BPEL4WS提供了一组可以在流程中使用的基本活动和结构化活动。
To edit WSDL files required for deploying a BPEL4WS process, you can use other tools.
要编辑部署BPEL4WS流程所需的WSDL文件，您可以使用其他工具。
For a more detailed description, please see the BPEL4WS series cited in the resources.
要获得更详细的描述，请参阅参考资料中引用的BPEL4WS系列。
Of these, the BPWS4J editor allows you to create the BPEL4WS file describing the process.
在上述这些部分当中，BPWS4J编辑器允许您创建描述流程的BPEL4WS文件。
This implementation can serve as a testbed for users to learn and experiment with BPEL4WS.
用户在学习和试验BPEL4WS时可以用这个实现来充当试验地。
Feature group names, identified in the analysis section, can map to conditions in BPEL4WS.
分析部分中确定的功能组名称可以映射到BPEL4WS中的条件。
Instead, instances in BPEL4WS are created implicitly when messages arrive for the service.
相反，BPEL4WS中的实例是在服务的消息到达时隐式地创建的。
A BPEL4WS process interacts with other Web services using invoke, receive and reply activities.
BPEL4WS流程使用调用(invoke)、接收(receive)和应答(reply)活动与其他Web服务进行交互。
The BPWS4J engine does not implement the entire BPEL4WS spec and that has caused a few problems.
BPWS4J引擎没有实现整个BPEL4WS规范，而且已经引起了一些细小的问题。
On the other hand, BPEL4WS offers the following advanced features that RosettaNet does not yet have.
在另一方面，BPEL4WS提供了以下RosettaNet还不具有的高级功能。
The root node of the process definition is the process element, as required by the grammar of BPEL4WS.
该流程定义的根节点是process元素，这是BPEL4WS的语法所要求的。
The fault concept on BPEL4WS is directly related to the fault concept on WSDL and in fact builds on it.
BPEL4WS的故障概念与WSDL 的故障概念有直接联系，事实上，前者建立在后者的基础上。
The BPEL4WS and WSDL paradigm provides its own methods for encoding, transporting, and securing messages.
BPEL4WS和WSDL范例提供了它自己的方法来编码、传输和保护消息。
The business process flow and mediation logic should be carefully separated into distinct BPEL4WS processes.
业务流程流和中介逻辑应该谨慎的分为不同的BPEL4WS流程。
At a conceptual level, a BPEL4WS process interacts with partners to receive, invoke, and reply to activities.
从概念上讲，BPEL4WS流程是通过与合作伙伴交互来接收、调用和应答活动的。
The profile allows developers to use normal UML skills and tools to develop Web services processes using BPEL4WS.
配置文件允许开发者使用常规的UML技巧和工具，开发基于BPEL4WS的Web服务业务流程。
应用推荐