Browse Prior Art Database

Asynchronous Compensation for Compensation Scopes Disclosure Number: IPCOM000031974D
Original Publication Date: 2004-Oct-18
Included in the Prior Art Database: 2004-Oct-18
Document File: 1 page(s) / 4K

Publishing Venue



Compensation scopes are a fundamental concept in business process languages, such as Business Process Execution Language for Web Services (BPEL4WS). The effects of the activities within a compensation scope are undone by running a compensation handler associated with the scope. When a compensation scope is compensated, navigation halts until compensation has completed. It is suggested that users should have the option to specify that compensation should be done asynchronously. This allows the navigation to immediately continue providing significant performance improvements with respect to process execution time.

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

Page 1 of 1

Asynchronous Compensation for Compensation Scopes Asynchronous Compensation for Compensation ScopesAsynchronous Compensation for Compensation Scopes Asynchronous Compensation for Compensation Scopes

There are several options how a user could model/define the behavior that compensation of compensation scopes are done asynchronously . Asynchronously means that navigation does not wait until compensation has completed . Specification of the desired behavior could be done similar to other settings, such as the suppressJoinFailure attribute).

An attribute on the process level indicates that compensation for all


compensation scopes is done asynchronously. This constitutes then the default behavior (similar to the suppressJoinFailure attribute); it can be overwritten on the compensation scope level
An attribute on the compensation scope level. This constitutes then the behavior


of the associated compensation scope and possibly the behavior of the enclosed compensation scopes.