Abstract

Web Services are important for integrating distributed heterogeneous applications. One of the problems that facing Web Services is the difficulty for a service provider to represent the datatype of the parameters of the operations provided by a Web service inside Web Service Description Language (WSDL). This problem will make it difficult for service requester to understand, reverse engineering, and also to decide if Web service is applicable to the required task of their application or not. This paper introduces an approach to extend Web service datatypes specifications inside WSDL in order to solve the aforementioned challenges. This approach is based on adding more description to the provided operations parameters datatypes and also simplified the WSDL document in new enrichment XML-Schema. The main contributions of this paper are: 1. Comprehensive study of 33 datatypes in C# language, and how they are represented inside WSDL document. 2. Classification of the previous mentioned datatypes into 3 categories: ( Clear, Indistinguishable, and Unclear ) datatypes. 3. Enhance the representation of 18% of C# datatypes that are not supported by XML by producing a new simple enrichment XML-based schema. 4. Enhance Web Service Understandability by simplifying WSDL document through producing summarized new simple enrichment schema.

Highlights

  • WHAT ARE WEB SERVICES?A review of the various studies showed that a large number of definitions for Web Service have been proposed

  • This fact has caused Service Requesters to question the trustworthiness of Web Service because Service Requesters do not trust Web Services that were implemented by others without seeing the source code. [6] mentioned that this problem is limiting the growth of Web Service applications and that these applications will not grow unless researchers meet this trustworthiness challenge. [7] stated that the current methods and technologies cannot ensure Web Service trustworthiness and that for Web Services to grow, researchers must address this challenge

  • The tool can be auto run when the user tries to bind with the Web Service. This tool can answer the major question of this paper, that is: Can we extend the XML Schema datatypes to reach for a better comprehension of the Web Service Description Language (WSDL) documents by the service requester and provider of Web Services? Other questions could be inspired from the previous major question, such as: a) Do all of the parameters datatypes need to be extended ?

Read more

Summary

INTRODUCTION

A review of the various studies showed that a large number of definitions for Web Service have been proposed. Each service has its self-located, self-describing and self-operational properties If one of these endpoints is to provide service over network (Internet or intranet), the provider must publish a full and detailed explanation for this service. WSDL makes it easier for other endpoints which share the same network to know more about the provided service, and to decide if this service is applicable for their needs or not Web Service faces numerous challenges and problems, including, but not limited to the following [5]: a) The trustworthiness problem: The Service Requester can only see the contract (WSDL) of a Web Service but not the source code. [6] mentioned that this problem is limiting the growth of Web Service applications and that these applications will not grow unless researchers meet this trustworthiness challenge.

RELATED WORK
Overview
Reverse Engineering Approach for Semantic Web Services Composition
Model-Driven Web Service Development
Reverse Engineering Existing Web Service Applications
THE PROPOSED MODEL
TOOL ENVIRONMENT
CONCLUSION AND FUTURE WORK
Conclusions
Findings
Future work

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.