Building Reliable Web Services Compositions

Pires, Paulo F.; Benevides, Mario R. F.; Mattoso, Marta

doi:10.1007/3-540-36560-5_5

Cited by 66 publications

(49 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…A Web service is a self-contained modular program built with XML, SOAP, WSDL and UDDI specifications that can be discovered and invoked across the Internet ( [6,7]). A transactional Web service is a Web service that emphasizes transactional properties for its characterization and correct usage.…”

Section: Transactional Composite Web Services 31 Transactional Web Smentioning

confidence: 99%

Overview of Transactional Patterns: Combining Workflow Flexibility and Transactional Reliability for Composite Web Services

Bhiri

Gaaloul

Perrin

et al. 2005

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. In this paper, we present an approach to easily define flexible and reliable services compositions. We introduce a new concept called transactional patterns to specify flexible and reliable composite Web services. A transactional pattern is a convergence concept between workflow patterns and advanced transactional models. It can be seen as a coordination pattern and as a structured transaction. Thus, it combines workflow flexibility and transactional processing reliability. Designers can simply connect together a set of transactional patterns to define a composite Web service. We use a set of techniques to ensure control and transactional coherence between patterns inside a services composition.

show abstract

Section: Transactional Composite Web Services 31 Transactional Web Smentioning

confidence: 99%

Overview of Transactional Patterns: Combining Workflow Flexibility and Transactional Reliability for Composite Web Services

Bhiri

Gaaloul

Perrin

et al. 2005

Lecture Notes in Computer Science

View full text Add to dashboard Cite

show abstract

“…Typical Web service applications include business-to-business integration (B2B), business process integration and management, e-sourcing and content distribution. Web service interfaces and bindings are defined, described and discovered by XML parsers, supporting direct XML message-based interactions with other services and applications via Internet-based protocols like SOAP [30]. Standards for service description and discovery such as the Universal Description Discovery and Integration (UDDI) [33] specification are designed to function in a fashion similar to white pages or yellow pages, where businesses and services can be looked up by name and/or by standard service taxonomy.…”

Section: Introductionmentioning

confidence: 99%

Personalized Web Service Selection

Khapre¹,

Dhasarathan²

2011

IJWesT

View full text Add to dashboard Cite

show abstract

“…Then, a client (the service composer), or a middleware service acting on behalf of a client, may exploit those descriptions for specifying and executing a (open-nested) transaction over a set of Web services whose termination is dictated by the outcomes of the transactional operations invoked on the individual services. Such a concern is particularly addressed in the WSTx [15] and WebTransact [18] frameworks. However, these approaches are not sufficient for comprehensively expressing the recovery behavior of a service.…”

Section: Specifying Recovery Behavior Of Web Servicesmentioning

confidence: 99%

“…The language introduced in [2] allows specifying transactional behavior of conversations. However, it uses a list of pre-defined transactional properties in a way similar to approaches that annotates individual operations with transactional properties [15,18], hence reducing the language's expressiveness. Furthermore, existing conversation languages do not address timing issues, except for CS-WS [9] that introduces an additional timeout attribute associated to operations.…”

Section: Related Workmentioning

confidence: 99%