IBM Systems Journal
Production workflow: concepts and techniques
Production workflow: concepts and techniques
Web Services Platform Architecture: SOAP, WSDL, WS-Policy, WS-Addressing, WS-BPEL, WS-Reliable Messaging and More
Enterprise SOA: Service-Oriented Architecture Best Practices (The Coad Series)
Enterprise SOA: Service-Oriented Architecture Best Practices (The Coad Series)
WSDL 2.0 Message Exchange Patterns: Limitations and Opportunities
ICIW '08 Proceedings of the 2008 Third International Conference on Internet and Web Applications and Services
Extending BPELlight for Expressing Multi-Partner Message Exchange Patterns
EDOC '08 Proceedings of the 2008 12th International IEEE Enterprise Distributed Object Computing Conference
Formalising Message Exchange Patterns using BPEL Light
SCC '08 Proceedings of the 2008 IEEE International Conference on Services Computing - Volume 1
BPM'07 Proceedings of the 5th international conference on Business process management
Web Services: Concepts, Architectures and Applications
Web Services: Concepts, Architectures and Applications
Conversational Web Services: leveraging BPELlight for expressing WSDL 2.0 message exchange patterns
Enterprise Information Systems - Towards Model-driven Service-oriented Enterprise Computing - 12th International IEEE EDOC Enterprise Computing Conference (EDOC 2008)
Hi-index | 0.00 |
BPELlight is an extension of BPEL that allows defining executable business processes independant of WSDL port types and operations. However, it adopts BPELs principle of having either non-blocking activities that only send or receive a single message or blocking activities, that are restricted to at most two messages, i.e. they implement a send-receive or receive-send behaviour. In recent work BPELlight has been used to define arbitrary complex message exchange patterns. In this paper we use message exchange patterns defined in BPELlight to describe the behaviour of interaction activities in a generic manner. This is beneficial as complex behaviour like a "request-for-bid" only have to be modelled once on an abstract level and can then be reused by simply referencing the corresponding message exchange pattern and filling in parameters whenever needed. This makes process modelling more convenient as the modelling primitives are not restricted to a request-response behaviour but are lifted to a business oriented level.