BPEL 1.1 vs BPEL 2.0
If you already have BPEL 1.1 in a BPEL project it wont accept BPEL 2.0 in the same BPEL service. But in a composite you can have two services one with BPEL 1.1 and another with BPEL 2.0.
• <forEach> activity to repeat the set of activities . Replace the FlowN activity in BPEL 1.1 version.
• <repeatUntil> - Use this activity if the body of an activity must be performed at least once. The XPath expression condition in the repeatUntil activity is evaluated after the body of the activity completes.
• <if>-<elseif>-<else> - Replaces the switch activity in BPEL 2.0 - This activity enables you to define conditional behavior for specific activities to decide between two or more branches. Only one activity is selected for execution from a set of branches.
• Changed <terminate> to <exit>
• <compensateScope> - to compensate the specified child scope
• A <rethrow> activity has been added to fault handlers this activity enables you to
rethrow a fault originally captured by the immediately enclosing fault handler.
• BPEL 2.0 adds a new simplified XPath notation ($variableName) replacing the
getVariableData() function.
If you already have BPEL 1.1 in a BPEL project it wont accept BPEL 2.0 in the same BPEL service. But in a composite you can have two services one with BPEL 1.1 and another with BPEL 2.0.
• <forEach> activity to repeat the set of activities . Replace the FlowN activity in BPEL 1.1 version.
• <repeatUntil> - Use this activity if the body of an activity must be performed at least once. The XPath expression condition in the repeatUntil activity is evaluated after the body of the activity completes.
• <if>-<elseif>-<else> - Replaces the switch activity in BPEL 2.0 - This activity enables you to define conditional behavior for specific activities to decide between two or more branches. Only one activity is selected for execution from a set of branches.
• Changed <terminate> to <exit>
• <compensateScope> - to compensate the specified child scope
• A <rethrow> activity has been added to fault handlers this activity enables you to
rethrow a fault originally captured by the immediately enclosing fault handler.
• BPEL 2.0 adds a new simplified XPath notation ($variableName) replacing the
getVariableData() function.
The fbelow three activities has been removed in BPEL 2.0 and validate activity has been
changed to a BPEL Construct in BPEL 2.0
Bind Entity
Create Entity
Remove Entity
No comments:
Post a Comment