Asynchronous messaging between Web services using SSDL

Parastatidis, Savas; Woodman, Simon; Webber, Jim; Kuo, Dean; Greenfield, Paul

doi:10.1109/mic.2006.3

Cited by 18 publications

(14 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Although we concentrate on LTL, our approach is general: many other languages can be mapped into equivalent LTL expressions, or extensions thereof; this includes, among others, Message Sequence Charts [18], SSDL's Message Exchange Patterns (MEP) and Rules protocol frameworks [19], and the Let's Dance choreography description language [20].…”

Section: Formalizing Message Contractsmentioning

confidence: 99%

Runtime Enforcement of Web Service Message Contracts with Data

Hallé

Villemaire

2012

IEEE Trans. Serv. Comput.

View full text Add to dashboard Cite

Abstract-An increasing number of popular SOAP web services exhibit a stateful behavior, where a successful interaction is determined as much by the correct format of messages as by the sequence in which they are exchanged with a client. The set of such constraints forms a "message contract" that needs to be enforced on both sides of the transaction; it often includes constraints referring to actual data elements inside messages. We present an algorithm for the runtime monitoring of such message contracts with data parameterization. Their properties are expressed in LTL-FO þ , an extension of Linear Temporal Logic that allows first-order quantification over the data inside a trace of XML messages. An implementation of this algorithm can transparently enforce an LTL-FO þ specification using a small and invisible Java applet. Violations of the specification are reported on-the-fly and prevent erroneous or out-of-sequence XML messages from being exchanged. Experiments on commercial web services from Amazon.com and Google indicate that LTL-FO þ is an appropriate language for expressing their message contracts, and that its processing overhead on sample traces is acceptable both for client-side and server-side enforcement architectures.

show abstract

Section: Formalizing Message Contractsmentioning

confidence: 99%

Runtime Enforcement of Web Service Message Contracts with Data

Hallé

Villemaire

2012

IEEE Trans. Serv. Comput.

View full text Add to dashboard Cite

show abstract

“…While WS-BPEL represent the workflow orchestrated by a dominating entity (the BPEL engine running the BPEL script), WS-CDL defines the same workflow as a protocol between services which are independent peers working together to realize a collaboration: WS-CDL definition can be decomposed in different BPEL scripts, each one executed by a peer in the collaboration. Recently, two other languages have been proposed: SOAP Service Description Language (Parastatidis, 2006) which enables contract specification on WSDL 2.0 and it is better suited to precisely specify a web service interface than representing an orchestration language; Taverna (Wolstencroft, 2005) is a data-centric workflow language which uses data dependencies to describe a workflow of GRID processes. Any of these XML-based languages is not so useful without a related service creation environment, used to generate such languages from a high-level, possibly graphical, representation Regarding the service creation environment, WebSphere Studio Application Developer (IBM, 2007) and RapidFLEX Application Server (Pactolus, 2001) provide a graphical SCE easing the service creation process of value added services.…”

Section: Service Description Languagesmentioning

confidence: 99%

Communication Web Services and JAIN-SLEE Integration Challenges

Falcarin

Venezia

2008

International Journal of Web Services Research

View full text Add to dashboard Cite

ABSTRACT:Meshing up telecommunication and IT resources seems to be the real challenge for supporting the evolution towards the next generation of Web Services. In telecom world, JAIN-SLEE (JAIN Service Logic Execution Environment) is an emerging standard specification for Java service platforms targeted to host value added services, composed of telecom and IT services. In this paper we describe StarSLEE platform which extends JAIN-SLEE in order to compose JAIN-SLEE services with Web services and the StarSCE service creation environment which allows exporting value added services as communication web services, and we analyze open issues that must be addressed to introduce Web Services in new telecom service platforms.

show abstract

“…To describe more complex interactions, additional specifications such as WS-BPEL [13] or WS-Choreography [26] have to be used in addition to WSDL. Unfortunately, this further increases the complexity of the Web Service description [21].…”

Section: Why Ssdl?mentioning

confidence: 99%

“…Making this information available to consumers promotes protocol-based integration [21] rather than interface-centric solutions. Currently, four protocol frameworks -MEP (Message Exchange Pattern) [18], CSP (Communicating Sequential Processes) [17], Rules [8] and SC (Sequencing Constraints) [32] -have been specified, but additional protocol frameworks can be created and plugged into SSDL, if needed.…”

Section: Ssdl Language Featuresmentioning

confidence: 99%

“…It is thus crucial that this description is exposed, so interested parties can retrieve it and reason about the described service. This reasoning might range from simply checking a Web Service's compatibility to performing protocol-based integration of services [21]. The previous sections have suggested that Soya can infer SSDL from the service classes and attribute metadata.…”

Section: Exposing Ssdl Contractsmentioning

confidence: 99%

See 1 more Smart Citation

Soya: A Programming Model and Runtime Environment for Component Composition Using SSDL

Fornasier

Webber²,

Gorton

2007

Component-Based Software Engineering

View full text Add to dashboard Cite

Abstract. The SOAP Service Description Language (SSDL) is a SOAPcentric language for describing Web Service contracts. SSDL focuses on message abstraction as the building block for creating service-oriented applications and provides an extensible range of protocol frameworks that can be used to describe and formally model component composition based on Web Service interactions. Given its novel approach, implementing support for SSDL contracts presents interesting challenges to middleware developers. At one end of the spectrum, programming abstractions that support message-oriented designs need to be created. At the other end, new functionality and semantics must be added to existing SOAP engines. In this paper we explain how component developers can create message-oriented Web Service interfaces with contemporary tool support (specifically the Windows Communication Foundation) using SSDL. We show how SSDL can be used as an alternative and powerful metadata language natively alongside existing tooling without imposing additional burdens on application developers. Moreover, we describe the design and architecture of the Soya middleware which supports SSDLbased development of Web Services on the WCF platform.

show abstract

Asynchronous messaging between Web services using SSDL

Cited by 18 publications

References 2 publications

Runtime Enforcement of Web Service Message Contracts with Data

Runtime Enforcement of Web Service Message Contracts with Data

Communication Web Services and JAIN-SLEE Integration Challenges

Soya: A Programming Model and Runtime Environment for Component Composition Using SSDL

Contact Info

Product

Resources

About