Thursday, 22 February 2018

Differences between BPEL1.1 and BPEL2.0Versions summarized

Hi All,

Both SOA suite 11g and 12c provides the users to use BPEL1.1 and 2.0 versions when creating a bpel process.

    BPEL 1.1                                                BPEL 2.0

1. We have Flow and FlowN                  1. We have Flow and <forEach>
2. <if>- <elseif>- <else>                        2. Replaced by Switch Activity
3. <terminate>                                        3. Replaced by <exit> Activity
4. No such activity                                 4. New activity <compensateScope> has been added
5. No such activity                                 5. Rethtrow Activity has been added to the Fault Handlers
6. No such activity                                 6. RepeatUntil Activity has been newly added. We canuse                                                                           this if we want the body of the activity to be executed                                                                             atleast once.

Other important differences are as noted below:

1. In BPEL 1.1 there is no defined behavior for a process that receives a message for a request-response operation and finishes without replying.
Similar scenario in BPEL 2.0 would have trigged a Fault message.

2. Xpath expressions are simplified using '$' while accessing variables in BPEL2.0
EX. $OutputVariable.payload/ns4:Result

Where as in BPEL 1.1 it is something like
EX: (bpws:getVariableData('OutputVariable','payload','/ns4:Result')

3.BPEL2.0 support multipart WSDL messages.
    a. toParts element in invoke and reply activities provides an alternative to explicitly creating                    multipart WSDL messages from the contents of BPEL variables
    b. The fromParts element retrieves data from an incoming multipart WSDL message and places               the data into individual variables


Hope this summarizes most of the points.. If missed anything kindly add in comment section.

Let's explore SOA! :)


No comments:

Post a Comment