An approach to validating transactional properties of WS-BPEL composition

Shi Ting Wen, Qing Li, Lihua Yue, An Liu

Research output: Chapter in book / Conference proceedingConference article published in proceeding or bookAcademic researchpeer-review

1 Citation (Scopus)

Abstract

As composite web services are often long lasting, loosely coupled, cross application and administrative boundaries, transactional support to integrated business via composing individual web services is a critical issue. Currently, WS-BPEL which is more expressive than traditional workflow language, has been the de facto standard for web service composition. However, most works on transactional properties focus on structured workflows, and there is no tool to validate transactional properties for WS-BPEL processes. In this paper, we present a technique to analyze WS-BPEL files to validate whether a process complies with the expected transactional properties. We identify key point and risk point to help validate whether a process is well-formed. The validation technique can assess the correctness of WS-BPEL process specifications and therefore can help process designers to identify ill-formed processes.

Original languageEnglish
Title of host publicationSKG 2009 - 5th International Conference on Semantics, Knowledge, and Grid
Pages216-223
Number of pages8
DOIs
Publication statusPublished - 1 Dec 2009
Externally publishedYes
Event5th International Conference on Semantics, Knowledge, and Grid, SKG 2009 - Zhuhai, China
Duration: 12 Oct 200914 Oct 2009

Publication series

NameSKG 2009 - 5th International Conference on Semantics, Knowledge, and Grid

Conference

Conference5th International Conference on Semantics, Knowledge, and Grid, SKG 2009
Country/TerritoryChina
CityZhuhai
Period12/10/0914/10/09

ASJC Scopus subject areas

  • Computer Networks and Communications
  • Software

Fingerprint

Dive into the research topics of 'An approach to validating transactional properties of WS-BPEL composition'. Together they form a unique fingerprint.

Cite this