Communicating sequential processes
Communications of the ACM
POPL '79 Proceedings of the 6th ACM SIGACT-SIGPLAN symposium on Principles of programming languages
Unraveling the Web Services Web: An Introduction to SOAP, WSDL, and UDDI
IEEE Internet Computing
E-services: a look behind the curtain
Proceedings of the twenty-second ACM SIGMOD-SIGACT-SIGART symposium on Principles of database systems
Composing Web Services with PEWS: A Trace-Theoretical Approach
ECOWS '06 Proceedings of the European Conference on Web Services
Finite State Automata As Conceptual Model For E-Services
Journal of Integrated Design & Process Science
A theory of contracts for web services
Proceedings of the 35th annual ACM SIGPLAN-SIGACT symposium on Principles of programming languages
Dependence graphs for verifications of web service compositions with PEWS
Proceedings of the 2008 ACM symposium on Applied computing
Formal semantics and expressiveness of a web service composition language
Proceedings of the 28th Annual ACM Symposium on Applied Computing
| Hi-index | 0.00 |
PEWS is a programming language for the definition of web service interfaces. PEWS programs can be used for the description of both simple and composite web services. Simple web services can be built from scratch, by the combination of (WSDL) operations. Each operation must be implemented as a Java method. Composite web services are constructed from the combination of existing web services, accessed by using their WSDL descriptions. PEWS combinators help to define the order in which web services and operations will be performed. PEWS has a human-readable syntax as well as a XML version, called XPEWS. The human-readable language is intended to help in the design of web services and in the formal reasoning about programs. XPEWS is used as an interface language between the front-end and back-end of the PEWS language processor. This paper presents the development of a computational environment for PEWS. The front-end of the environment is an Eclipse plug-in. The use of the front-end can help reducing the time for development of the compositions, by the verification of codification errors and the generation XPEWS documents. The back-end of PEWS is responsible for the implementation of the web services described in a XPEWS document. The back-end produces Java™ code (skeletons) to call the web service operations and performs them in the order defined by the XPEWS document.