Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Using scopes for specifying integrity boundaries

IP.com Disclosure Number: IPCOM000029062D
Original Publication Date: 2004-Jun-15
Included in the Prior Art Database: 2004-Jun-15
Document File: 1 page(s) / 33K

Publishing Venue

IBM

Abstract

Business Process Execution Language for Web Services (BPEL4WS) is an evolving OASIS standard for defining business processes that orchestrate the execution of Web Services. The language provides the notion of scopes that enclose a set of activities. Scopes are associated with properties that define how the scope is to be processed. For example the property variableAccessSerializable="yes" indicates that two scopes defined with this property need to be carried out one after the other if they access at least one common variable. It is suggested that scopes are also used to specify integrity boundaries. For example one could specify that the enclosed variables are checked for XML schema correctness when the flow of control leaves the scope.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 74% of the total text.

Page 1 of 1

Using scopes for specifying integrity boundaries

Business Process Execution Language for Web Services (BPEL4WS) is an evolving OASIS standard for defining business processes that orchestrate the execution of Web Services. The language provides the notion of scopes. Scopes enclose a set of activities. The purpose of scopes is to define processing that applies to all of the enclosed activities or to define a particular processing behavior that applies to the scope. For example, a scope may have the property variableAccessSerializable. This property indicates that two peer (parallel) scopes that have this property set to yes, need to be executed one after the other (serialized) when the first scope touches a variable that is used by both scopes. A detailed explanation of the property can be found in the appropriate BPEL 4WS specifications.

    Variables in BPEL4WS can be of three types: WSDL (Web Services Description Language) messages, XML simple types, or XML complex types. They are manipulated using <assign> activities or via the invocation of a Web Service . During the manipulation of an activity, it is possible that for some period of time that the actual content of the variable violates the underlying XML schema . This mandates a mechanism that helps to identify when a variable should be checked for conformance with its underlying XML schema (or WSDL message type). It is proposed that scopes are being used for defining that mechanism by adding an additional attrib...