Page Operations
Browse Space
BPEL Client & Implementation Model
The SCA WS-BPEL Client and Implementation model specifies how WS-BPEL processes can be used with SCA, both as service implementations and as service clients. The goal of the specification is to address the following scenarios.
Start from WS-BPEL process. It should be possible to use any valid WS-BPEL 2.0 process definition as the implementation of a component within SCA. In particular, it should be possible to generate an SCA Component Type from any WS-BPEL process definition and use that type within an SCA assembly. Most BPEL4WS 1.1 process definitions may also be used with SCA by using the backward compatibility approach described in the specification.
Start from SCA Component Type. It should be possible to use WS-BPEL to implement any SCA Component Type that uses only WSDL interfaces to define services and references, possibly with some SCA specific extensions used in process definition.
Start from WS-BPEL with SCA extensions. It should be possible to create a WS-BPEL process definition that uses SCA extensions and generate an SCA Component Type and use that type within an SCA assembly. Some SCA capabilities (such as properties and multi-party references) can only be used by WS-BPEL process definitions that use SCA extensions.
What's New?
The BPEL Client and Implementation specification is new, created since the publication of the V0.9 SCA specifications. The main goal of the specification is to describe how any valid BPEL process can be used as the implementation of a component within SCA. The most important aspect is the description of how to map BPEL's partner links to SCA services and references. The specification also defines some optional BPEL extensions that can be used to access SCA concepts that have no equivalent standard BPEL construct, such as deployment-time properties and multi-valued references.
