WS-BPEL 2.0 Object Properties

Counter name

[forEach] Specifies the variable used by the <<forEach>> activity to store the counter of the loop. During each repetition, the "xsd:unsignedInt" variable is implicitly declared in the activity's child <<scope>>. The name of the implicit variable is specified in the CounterName attribute.

Scripting name: CounterName

Create instance

[receive and pick] Specifies the instanciation of the process.

Default value: No

Scripting name: CreateInstance

Data schema target namespace

[WSDL file] Specifies the target namespace of the data schema.

Scripting name: schemaNameSpace

Definition namespace

[message format] Specifies the namespace URI message that can only be used by BPEL variables.

Default variable: %ownerServiceNmspc%

Scripting name: DefinitionNamespace

Definition target namespace

[model and package] Specifies the target namespace.

Default value: %urnName%

Scripting name: DefinitionTargetNamespace

Exit on standard fault

[scope, sequence, flow and if] When set to "yes" on a scope, the process must exit immediately.

Default value: No

Scripting name: ExitOnStandardFault

Expression language

Specifies the expression language used in expressions.

Default value: urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0

Scripting name: expressionLanguage

Final counter expression

[forEach] Computes the final value of the counter variable used by the <<forEach>> activity. It is evaluated when the activity starts.

Scripting name: FinalCounterExpression

First correlation pattern

[invoke] When the first correlation is used by the invoke activity, you can choose between one of the following values:

• request
• request-response
• response

Scripting name: InCorrelationPattern

Imported WSDL content

[WSDL file] Specifies the content of the original reversed WSDL file.

Scripting name: ImportedWsdlContent

Isolated

[scope, sequence, flow and if] 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: Isolated

Initiate correlation

Scripting name: InitiateCorrelation

Initiate input correlation

[invoke] When the first correlation is used by the invoke activity, you can choose between one of the following values for the initiate attribute:

• yes
• no
• join

Scripting name: InCorrelationInitiate

Initiate output correlation

[invoke] When the second correlation is used by the invoke activity, you can choose between one of the following values for the initiate attribute:

• join
• no
• yes

Scripting name: OutCorrelationInitiate

Join condition

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.

Scripting name: joinCondition

Multiple correlation

Specifies a BPEL Invoke, Receive or Reply using multiple correlation keys.

Scripting name: MultipleCorrelation

Name

[partner link type] Specifies the name of the partner link type.

Scripting name: PartnerLinkTypeName

Namespace prefix to use

[XSD document and WSDL file] Specifies the XML prefix used by the process to reference the schema definition or service provider.

Default variable: %wsdlUsedPref%

Scripting name: PrefixForUse

Organization unit role

[partner link type] Specifies the role played by a partner in the collaboration. When undefined, the generated role is the name of the organization unit.

Scripting name: OrganizationUnitRole

Process role

[partner link type] Specifies the role played by the process in the collaboration. When undefined, the generated role is the name of the process.

Scripting name: ProcessRole

Parallel

[forEach] Specifies whether the activity is serial or parallel.

Default value: No

Scripting name: Parallel

Second correlation pattern

[invoke] When the second correlation is used by the invoke activity, you can choose between one of the following values:

• request
• request-response
• response

Scripting name: OutCorrelationPattern

Start counter expression

[forEach] Computes the initial value of the counter variable used by the <<forEach>> activity. It is evaluated when the activity starts.

Scripting name: StartCounterExpression

Successful branches only

[forEach] Specifies whether to count all scopes or only those which have completed successfully. The <branches> element of the forEach activity represents an unsigned-integer expression used to specify a completion condition.

Default value: No

Scripting name: SuccessfulBranchesOnly

Suppress join failure

Specifies 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.

Default value: No

Scripting name: suppressJoinFailure

Validate

[Assign] Specifies whether the assign activity validates all the variables being modified by the activity.

Default value: No

Scripting name: Validate