2005Unpublished venueRequires access

A Foundational Mechanism for WS-BPEL Recovery Framework

Roberto Lucchi, Manuel Mazzara

Open publisher page 3 citations

Abstract

Recently, the term Web services orchestration has been introduced to address some issues related to Web services composition, that is the way of deflning a complex service out of simpler ones. Several proposals for describing orchestration for business processes have been presented in the last years and many of these languages make use of concepts as long-running transactions and compensations for coping with error handling. WS-BPEL 2.0, the most credited candidate for becoming a standard, provides three difierent mechanisms allowing to cope with abnormal situations: exception, event and compensation handling. This complexity makes it di‐cult to formally deflne the framework, thus limiting the formal reasoning about the designed applications. In this paper we advocate that three difierent mechanisms for error handling are not necessary and we formalize a novel orchestration language based on the idea of event notiflcation as the unique error handling mechanism. To this end, we formally deflne the three BPEL mechanisms in terms of our calculus. It is possible to take advantages of this formal description in two ways. Firstly, this language represents by itself a proposal of simpliflcation for WS-BPEL 2.0 including an unambiguous speciflcation. Secondly, an implementor of an actual WS-BPEL 2.0 orchestration engine could implement simply this single mechanism providing all the remaining ones by compilation. With this attempt we intend to give a concrete contribute towards the improvement of the quality of the BPEL speciflcation, the applicability of BPEL itself and the implementation of real orchestration engines. Finally, as a case study we consider some of the hundreds of open issues met by the WS-BPEL designers and we propose a solution making use of the experience gained developing our algebra.

About this research paper

What this paper is about

Recently, the term Web services orchestration has been introduced to address some issues related to Web services composition, that is the way of deflning a complex service out of simpler ones. Several proposals for describing orchestration for business processes have been presented in the last years and many of these languages make use of concepts as long-running transactions and compensations for coping with error handling. WS-BPEL 2.0, the most credited candidate for becoming a standard, provides three difierent mechanisms allowing to cope with abnormal situations: exception, event and compensation handling. This complexity makes it di‐cult to formally deflne the framework, thus limiting the formal reasoning about the designed applications. In this paper we advocate that three difierent mechanisms for error handling are not necessary and we formalize a novel orchestration language based on the idea of event notiflcation as the unique error handling mechanism. To this end, we formally deflne the three BPEL mechanisms in terms of our calculus. It is possible to take advantages of this formal description in two ways. Firstly, this language represents by itself a proposal of simpliflcation for WS-BPEL 2.0 including an unambiguous speciflcation. Secondly, an implementor of an actual WS-BPEL 2.0 orchestration engine could implement simply this single mechanism providing all the remaining ones by compilation. With this attempt we intend to give a concrete contribute towards the improvement of the quality of the BPEL speciflcation, the applicability of BPEL itself and the implementation of real orchestration engines. Finally, as a case study we consider some of the hundreds of open issues met by the WS-BPEL designers and we propose a solution making use of the experience gained developing our algebra.

Why it matters

OpenAlex reports 3 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

Recently, the term Web services orchestration has been introduced to address some issues related to Web services composition, that is the way of deflning a complex service out of simpler ones. Several proposals for describing orchestration for business processes have been presented in the last years and many of these languages make use of concepts as long-running transactions and compensations for coping with error handling. WS-BPEL 2.0, the most credited candidate for becoming a standard, provides three difierent mechanisms allowing to cope with abnormal situations: exception, event and compensation handling. This complexity makes it di‐cult to formally deflne the framework, thus limiting the formal reasoning about the designed applications. In this paper we advocate that three difierent mechanisms for error handling are not necessary and we formalize a novel orchestration language based on the idea of event notiflcation as the unique error handling mechanism. To this end, we formally deflne the three BPEL mechanisms in terms of our calculus. It is possible to take advantages of this formal description in two ways. Firstly, this language represents by itself a proposal of simpliflcation for WS-BPEL 2.0 including an unambiguous speciflcation. Secondly, an implementor of an actual WS-BPEL 2.0 orchestration engine could implement simply this single mechanism providing all the remaining ones by compilation. With this attempt we intend to give a concrete contribute towards the improvement of the quality of the BPEL speciflcation, the applicability of BPEL itself and the implementation of real orchestration engines. Finally, as a case study we consider some of the hundreds of open issues met by the WS-BPEL designers and we propose a solution making use of the experience gained developing our algebra.

Key concepts: Business Process Execution Language, Computer science, Orchestration, Web service, Software engineering, Business process, Programming language, Distributed computing

Related papers

Back to paper searchBrowse research topicsOriginal source
A Foundational Mechanism for WS-BPEL Recovery Framework — Research Paper | ScholarLens