Conference Paper: Extending BPEL light for Expressing Multi-Partner Message Exchange Patterns

Bibliography

Jörg Nitzsche, Tammo van Lessen & Frank Leymann: “Extending BPEL light for Expressing Multi-Partner Message Exchange Patterns”, in Proceedings of the 12th IEEE International EDOC Conference (EDOC 2008), 2008, 245–254.

Keywords: BPEL; BPEL light; MEP; Message Exchange Pattern; Multi-Partner

Abstract

Message exchange patterns provide means to define the message flow of a service and how these messages are related in an abstract and reusable manner. They are an integral part of WSDL 2.0 and allow defining operations that have a message exchange beyond requestresponse. They reduce the impedance mismatch between imperative programming and message orientation while emphasizing the message orientated nature of Web Services. Whereas BPEL defines a flow between Web Service operations, BPELlight is an appropriate candidate to define the flow within operations since it abstracts from WSDL. In this paper we extended BPELlight to facilitate capturing complex multi-lateral message exchanges. We refine the partner model and relax the definition of a conversation to enable modelling conversations that involve different partner types. We also extend the language with a first-class construct that enables storing, querying and thus distinguishing addressing information related to multiple partner instances. This way we enable modelling message exchange patterns that capture business logic in a reusable manner on an abstract level like for instance a request for bid scenario or a business transaction for purchase.

Links

PDF PDF
Link http://www.lrz-muenchen.de/~edoc2008/

BibTeX

@inproceedings{INPROC-2008-44,
  author = {Nitzsche, Jörg and van Lessen, Tammo and Leymann, Frank},
  title = {Extending BPEL light for Expressing Multi-Partner Message Exchange Patterns},
  booktitle = {Proceedings of the 12th IEEE International EDOC Conference (EDOC 2008)},
  publisher = {IEEE Computer Society},
  institution = {University of Stuttgart, Faculty of Computer Science, Electrical Engineering, and Information Technology, Germany},
  pages = {245–254},
  etype = {Conference Paper},
  month = {sep},
  year = {2008},
  isbn = {978-0-7695-3373-5},
  keywords = {BPEL; BPEL light; MEP; Message Exchange Pattern; Multi-Partner},
  language = {English},
  cr-category = {H.4.1 Office Automation, K.1 The Computer Industry},
  ee = {http://www.lrz-muenchen.de/~edoc2008/},
  department = {University of Stuttgart, Institute of Architecture of Application Systems},
  abstract = {Message exchange patterns provide means to define the message flow of a service and how these messages are related in an abstract and reusable manner. They are an integral part of WSDL 2.0 and allow defining operations that have a message exchange beyond requestresponse. They reduce the impedance mismatch between imperative programming and message orientation while emphasizing the message orientated nature of Web Services. Whereas BPEL defines a flow between Web Service operations, BPELlight is an appropriate candidate to define the flow within operations since it abstracts from WSDL. In this paper we extended BPELlight to facilitate capturing complex multi-lateral message exchanges. We refine the partner model and relax the definition of a conversation to enable modelling conversations that involve different partner types. We also extend the language with a first-class construct that enables storing, querying and thus distinguishing addressing information related to multiple partner instances. This way we enable modelling message exchange patterns that capture business logic in a reusable manner on an abstract level like for instance a request for bid scenario or a business transaction for purchase.},
  url = {http://taval.de/publications/INPROC-2008-44}
}

© 2008 IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.