Messaging:- 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. In BPEL 2.0, such a scenario would have trigged a new BPEL standard fault called "missingReply" fault.
New activity types:- repeatUntil, validate, forEach (parallel and sequential), rethrow, extensionActivity, compensateScope
Renamed activities:- switch/case renamed to if/else, terminate renamed to exit
Termination Handler:- added to scope activities to provide explicit behavior for termination
Variable initialization
portType attribute:- The attribute "portType" of messaging activities such as "receive," "invoke," "reply," "pick," and "onEvent" is no longer mandatory and can be omitted
The XML element "compensationHandler" and the XML attribute "enableInstanceCompensation" in the top-level "process" element have been removed.Instance (process) level compensation handlers never had any mechanism for being invoked; therefore, because they could not be used instance level compensation handling is no longer supported.Replace XML attribute "variableAccessSerializable" with "isolated"
The URI used to specify XPath 1.0 as the expression/query language of choice has been changed, so replace the attribute value "http://www.w3.org/TR/1999/REC-xpath-19991116" of the attributes "expressionLanguage" and "queryLanguage" with the attribute value "urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"
Replace the XML attribute "variableAccessSerializable" with "isolated" .
XSLT for variable transformations (New XPath extension function bpws:doXslTransform).
Locally declared messageExchange (internal correlation of receive and reply activities) .
XPath access to variable data (XPath variable syntax $variable[.part]/location).
New activity types:- repeatUntil, validate, forEach (parallel and sequential), rethrow, extensionActivity, compensateScope
Renamed activities:- switch/case renamed to if/else, terminate renamed to exit
Termination Handler:- added to scope activities to provide explicit behavior for termination
Variable initialization
portType attribute:- The attribute "portType" of messaging activities such as "receive," "invoke," "reply," "pick," and "onEvent" is no longer mandatory and can be omitted
The XML element "compensationHandler" and the XML attribute "enableInstanceCompensation" in the top-level "process" element have been removed.Instance (process) level compensation handlers never had any mechanism for being invoked; therefore, because they could not be used instance level compensation handling is no longer supported.Replace XML attribute "variableAccessSerializable" with "isolated"
The URI used to specify XPath 1.0 as the expression/query language of choice has been changed, so replace the attribute value "http://www.w3.org/TR/1999/REC-xpath-19991116" of the attributes "expressionLanguage" and "queryLanguage" with the attribute value "urn:oasis:names:tc:wsbpel:2.0:sublang:xpath1.0"
Replace the XML attribute "variableAccessSerializable" with "isolated" .
XSLT for variable transformations (New XPath extension function bpws:doXslTransform).
Locally declared messageExchange (internal correlation of receive and reply activities) .
XPath access to variable data (XPath variable syntax $variable[.part]/location).
No comments:
Post a Comment