Top-Level Processes (BPEL)

BPEL top-level process property sheets contain all the standard process tabs, along with the BPEL tab, the properties of which are listed below:

Name

Description

Target namespace

Specifies the target namespace of the process which is necessary in the generated file.

Default value: %urnName%

Scripting name: targetNamespace

Definition namespace prefix

Specifies the prefix of the namespace that defines the BPEL definition file. The DefinitionTargetNamespace extended attribute on the Model defines the BPEL definition namespace.

Default value: %bpDefPrefix%

Scripting name: definitionNamespace

Expression language

Specifies the expression language used in the process.

Default value: [BPEL4WS] http://www.w3.org/TR/1999/REC-xpath-19991116 and [WS-BPEL] urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0

Scripting name: expressionLanguage

Query language

Specifies the XML query language used for selection of nodes in assignment, property definition, and other uses.

Default value: http://www.w3.org/TR/1999/REC-xpath-19991116

Scripting name: queryLanguage

Abstract process

Specifies whether the process being defined is abstract.

Default value: No

Scripting name: abstractProcess

[BPEL4WS] Variable access serializable

[WS-BPEL] Isolated

When 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 (or isolated)="yes" must be a leaf scope.

Default value: No

Scripting name: [BPEL4WS] variableAccessSerializable, [WS-BPEL] Isolated

[BPEL4WS] Enable instance compensation

Specifies whether the process instance as a whole can be compensated by platform-specific means.

Default value: No

Scripting name: enableInstanceCompensation

[WS-BPEL] Exit on standard fault

When set to "yes" on a scope, the process must exit immediately.

Default value: No

Scripting name: ExitOnStandardFault