Revising WSDL Documents: Why and How, Part 2

In a previous article, the authors demonstrated that effectively discovering Web services helps developers avoid several common design errors in Web Service Description Language (WSDL) documents. Their proposed guidelines are unfortunately applicable only when publishers follow the top-down, or cont...

Full description

Saved in:
Bibliographic Details
Published in:IEEE internet computing Vol. 17; no. 5; pp. 46 - 53
Main Authors: Mateos, C., Crasso, M., Zunino, A., Coscia, J. L. Ordiales
Format: Journal Article
Language:English
Published: New York, NY IEEE 01-09-2013
IEEE Computer Society
Subjects:
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:In a previous article, the authors demonstrated that effectively discovering Web services helps developers avoid several common design errors in Web Service Description Language (WSDL) documents. Their proposed guidelines are unfortunately applicable only when publishers follow the top-down, or contract-first, method of building services, which isn't very popular due to its inherent costs. Here, they present an approach for preventing such errors when using a counterpart method - namely, bottom-up or code-first - and measure the approach's impact on service discovery. The rationale behind the study is that because code-first service interfaces are automatically generated by tools that - given a service implementation - deterministically map programming language constructs onto WSDL elements, the measurable properties of service implementations could influence resulting service interfaces.
Bibliography:ObjectType-Article-2
SourceType-Scholarly Journals-1
ObjectType-Feature-1
content type line 23
ISSN:1089-7801
1941-0131
DOI:10.1109/MIC.2013.4