RESTful Web service composition with BPEL for REST

Abstract

a b s t r a c tCurrent Web service technology is evolving towards a simpler approach to define Web service APIs that challenges the assumptions made by existing languages for Web service composition. RESTful Web services introduce a new kind of abstraction, the resource, which does not fit well with the message-oriented paradigm of the Web service description language (WSDL). RESTful Web services are thus hard to compose using the Business Process Execution Language (WS-BPEL), due to its tight coupling to WSDL. The goal of the BPEL for REST extensions presented in this paper is twofold. First, we aim to enable the composition of both RESTful Web services and traditional Web services from within the same process-oriented service composition language. Second, we show how to publish a BPEL process as a RESTful Web service, by exposing selected parts of its execution state using the REST interaction primitives. We include a detailed example on how BPEL for REST can be applied to orchestrate a RESTful e-Commerce scenario and discuss how the proposed extensions affect the architecture of a process execution engine.

Correct-by-Construction Web Service Architecture

“…Most RESTful Web Services are not described using the standard WSDL language. The REST technology provides a new abstraction for publishing information and giving remote access to application systems: the resource [9]. It uses the inherent expressiveness of HTTP to retrieve representations of Web resources in varying states [12].…”

“…They expose a set of operations using two basic interaction patterns: synchronous invocation through remote procedure calls, and asynchronous interactions via message exchange [9]. SOAP-based services represent a procedural style of designing services as they require tightly coupled designs [10].…”

Near Field User Detection Strategy using Wi Fi BLE Networks

“…The server runs on Apache Tomcat 8.1 web application server. We make use of JERSEY 1.8 server and Spring Framework 3.1 for REST open API [11][12] [13][18] based attendance server implementation. Spring Framework provides an API so that developers may extend Spring to suit their needs.…”

Push-Enabling RESTful Business Processes

“…In our architecture we introduce a more general design based on hierarchically nested feeds. As opposed to our previous work on the BPEL for REST [22] and BPMN for REST [23] extensions, in this paper we propose an orthogonal approach to publish processes as resources which does not require to add any language features beyond the ability to control which tasks should be published as resources.…”