Chapter 10 Working with BPEL4WS
A top-level process defines a point of view of one partner collaborating with other partners. For example a seller can participate in different collaborations (with a buyer, with providers, or/and with carriers) and have a different role in each of the collaborations. These collaborations are designed using role associations between organization units (partners) and the top-level process (seller).
The following extended attributes (accessible from the BPEL4WS tab of the top-level process property sheet) apply to the top-level process:
| Name | Internal code | Description |
|---|---|---|
| Abstract process | abstractProcess | Specifies whether the process being defined is abstract. The default for this attribute is "no" |
| Enable instance compensation | enableInstanceCompensation | Determines whether the process instance as a whole can be compensated by platform-specific means. The default for this attribute is "no" |
| Expression language | expressionLanguage | This attribute specifies the expression language used in the process. The default for this attribute is XPath 1.0, represented by the URI of the XPath 1.0 specification: http://www.w3.org/TR/1999/REC-xpath-19991116 |
| Join condition | joinCondition | Each activity has optional standard attributes: a name, a join condition, and an indicator whether a join fault should be suppressed if it occurs. A join condition is used to specify requirements about concurrent paths reaching at an activity. The default value of the join condition (for the default expression language XPath) is the logical OR of the link status of all incoming links of this activity |
| Multiple correlation | MultipleCorrelation | Used to define BPEL Invoke, Receive or Reply using several correlation keys |
| Query language | queryLanguage | Specifies the XML query language used for selection of nodes in assignment, property definition, and other uses. The default for this attribute is XPath 1.0, represented by the URI of the XPath 1.0 specification: http://www.w3.org/TR/1999/REC-xpath-19991116 |
| Suppress join failure | suppressJoinFailure | Determines whether the joinFailure fault will be suppressed for all activities in the process. The effect of the attribute at the process level can be overridden by an activity using a different value for the attribute. The default for this attribute is "no" |
| Target namespace | targetNamespace | Used to define a target name space of the process necessary in the generated file |
| Variable access serializable | variableAccessSerializable | When this attribute is set to "yes", the scope provides concurrency control in governing access to shared variables. Such a scope is called a serializable scope. Serializable scopes must not be nested. A scope marked with variableAccessSerializable="yes" must be a leaf scope |
| Copyright (C) 2008. Sybase Inc. All rights reserved. |
| |