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...
Gespeichert in:
Veröffentlicht in: | IEEE internet computing 2013-09, Vol.17 (5), p.46-53 |
---|---|
Hauptverfasser: | , , , |
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
Zusammenfassung: | 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. |
---|---|
ISSN: | 1089-7801 1941-0131 |
DOI: | 10.1109/MIC.2013.4 |