Browse Prior Art Database

Finish Activities

IP.com Disclosure Number: IPCOM000126251D
Original Publication Date: 2005-Jul-11
Included in the Prior Art Database: 2005-Jul-11
Document File: 1 page(s) / 4K

Publishing Venue

IBM

Abstract

Business Process Execution Language for Web Services (BPEL4WS or BPEL for short) provides for the specification of business processes which invoke Web services and for providing business processes as Web services. It consists of a set of activities, whose sequence of execution is described by a graph. Scopes allow assigning properties to a set of activities; for example event handlers provide the capability to handle a set of messages independent of the current execution of the scope. It is suggested to add the notion of a activity to set of activity types. When a activity is executed within a scope, the scope is treated as successfully completed. If a activity is carried out in an event handler, the scope to which the event handler is attached to is also treated as successfully completed.

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

Page 1 of 1

Finish Activities Finish ActivitiesFinish Activities Finish Activities

Business Process Execution Language for Web Services (BPEL4WS or BPEL for short) provides for the specification of business processes which invoke Web services and for providing business processes as Web services . It consists of a set of activities, whose sequence of execution is described by a graph. Scopes allow assigning properties to a set of activities; for example event handlers provide the capability to handle a set of messages independent of the current execution of the scope.

    The language currently does not support the capability of terminating a scope successfully. Completion of a scope can only be achieved through execution of a <throw> activity that causes a fault to be thrown which then can be handled in an appropriate fault handler. The <terminate> activity unfortunately not only finishes the scope but the complete process. Further it is not possible to finish a scope through some external message received via an attached event handler. All these problems can be fixed through the introduction of a <finish> activity.

    When the <finish> activity is specified within a scope, the scope is treated as completed successfully; that means all outgoing connectors are treated as true .

    The <finish> activity can also be specified in an event handler attached to a scope. If the <finish> activity is executed, the scope is also treated as completed normally. This provides the capability to fini...