XML technologies for RESTful services development (original) (raw)

A framework for RESTful object exchange through schematized XML (unRESTricted)

2008 Third International Conference on Digital Information Management, 2008

Client-server architectures with clients on divergent platforms are in need of services that serve a high level of interoperability and a loose binding. It should be prevented that clients become incompatible with the server after server-side changes in the data model. In practice it appears that existing systems don't always meet these requirements and that known solutions are lacking supporting frameworks in the development of these services. This paper presents a framework for building RESTful services that publish data matching an internal object model. The internal objects are presented to the client by XML which conforms to an XML schema that is agnostic of the framework. The conversion between the XML documents and the internal objects is backed by the framework and abstracted from the service developer. An implementation of this framework in Java is described, together with client-side software that also relieves the client from marshaling logic and processing the server's response.

IRJET- Exploring REST and RESTful Web Services: A review

IRJET, 2020

In order to make powerful, reliable and user-friendly and web applications and web services, developing consolidated web applications is very important. In this paper we will showcase the goals of REST, the idea of REST and RESTful web service design principles and features of RESTful services with examples. In recent times, REST gained more popularity and is being widely used for web services development. Learning RESTful web Service can make the web development easier in many ways.

RESTful Web Services Development With a Model-Driven Engineering Approach

Advances in Computer and Electrical Engineering, 2019

A RESTful web service implementation requires following the constrains inherent to REST architectural style, which, being a non-trivial task, often leads to solutions that do not fulfill those requirements properly. Model-driven techniques have been proposed to improve the development of complex applications. In model-driven software development, software is not implemented manually based on informal descriptions but partially or completely generated from formal models derived from metamodels. A model-driven approach, materialized in a domain specific language that integrates the OpenAPI specification, an emerging standard for describing REST services, allows developers to use a design first approach in the web service development process, focusing in the definition of resources and their relationships, leaving the repetitive code production process to the automation provided by model-driven engineering techniques. The code generation process covers the entire web-service flow from ...

An XML Programming Language for Web Service Specification and Composition

IEEE Data(base) Engineering Bulletin - DEBU, 2001

XML is fast becoming the intergalactic data speak alphabet for data and information exchange that hides the heterogeneity among the components of Loosely-coupled, distributed systems and provides the glue that allows the individual components to take part in the loosely integrated system. Since much of this data is currently stored in relational database systems, simplifying the transformation of this data from and to XML in general and from and to the agreed upon exchange schema specifically is an important feature that should improve the productivity of the programmer and the efficiency of this process. This article provides an overview over the features that are needed to provide access via HTTP and XML and presents the approach taken in Microsoft SQL Server.

Migration of SOAP-based services to RESTful services

2011 13th IEEE International Symposium on Web Systems Evolution (WSE), 2011

Web services are designed to provide rich functionality for organizations and support interoperable interactions over a network. Web services are mainly realized in two ways: 1) SOAPbased services and 2) RESTful services. For the service providers, RESTful services can improve system flexibility, scalability, and performance as compared to the SOAP-based Web services. It is equally attractive to end users as it is consume less resources (i.e., battery, processor speed, and memory). Additionally, REST-based services do not include complex standards and heterogeneous operations; and hence are easier to consume and compose as compared to SOAP-based Web services. We provide an approach to migrate SOAP-based services to RESTful services. We identify resources from a SOAP-based Web service by analyzing its service description and mapping the contained operations to resources and HTTP methods. To demonstrate the effectiveness of our approach, we conduct a case study on a set of publicly available SOAP-based Web services. The results of our case study show that our approach can achieve high accuracy of identifying RESTful services from the interfaces of SOAP-based services. Our approach can improve the performance for invoking Web services after SOAP-based services are migrated to RESTful services.

Technology and Recent Development of XML Web Services

Service oriented architecture (SOA) is a flexible set of design principles used during the phases of systems development and integration. Upon deployment, an SOA-based architecture will provide a loosely-integrated suite of services that can be used within multiple business domains. SOA also generally provides a way for consumers of services, such as web-based applications, to be aware of available SOA-based services. For example, several disparate departments within a company may develop and deploy SOA services in different implementation languages, and their respective clients use a well understood, well defined interface to access them. XML is commonly used for interfacing with SOA services, though this is not required. It has been becoming one of the most widely used methodologies for building and integrating different types of software applications. This because the extreme benefits that it offers to their adopters including agility, dynamicity, and loose-coupling. These benefits are usually missed in traditional software terminologies and practices. XML Web Services is the most used technology for realizing SOA because it is easy to use. Furthermore, it allows high interoperability between different systems due to its dependency on standards that are widely accepted and supported by almost all large software vendors. However, XML Web Services suffers from a number of drawbacks such as low performance, bad utilization of hardware resources, and high network latency. These pitfalls may prevent some adopters from utilizing SOA in large and complex systems. Therefore, these issues should be first addressed and resolved before leveraging it into real-time systems. In this paper, an experimental evaluation for the performance of XML Web Services in real-time business systems is presented. In addition, this study offers some tactics and strategies that might be used to enhance the overall performance of XML Web Services. Furthermore, web service development as well as design analysis, modeling, and methodologies are presented. Moreover, the management and security of SOA are discussed.

Towards an MDA Mechanism for RESTful Services Development

2015

Automated software engineering research aspires to lead to more consistent software, faster delivery and lower production costs. Meanwhile, RESTful design is rapidly gaining momentum towards becoming the primal software engineering paradigm for the web, due to its simplicity and reusability. This paper attempts to couple the two perspectives and take the first step towards applying the MDE paradigm to RESTful service development at the PIM zone. A UML profile is introduced, which performs PIM meta-modeling of RESTful web services abiding by the third level of Richardson’s maturity model. The profile embeds a slight variation of the MVC design pattern to capture the core REST qualities of a resource. The proposed profile is followed by an indicative example that demonstrates how to apply the concepts presented, in order to automate PIM production of a system according to MOF stack. Next steps include the introduction of the corresponding CIM, PSM and code production.

RESTful, resource-oriented architectures: A model-driven approach

2011

RESTful Web services have opened the door to clients to use Web sites in ways the original designers never imagined giving rise to the mashup phenomenon. The main advantage of the model based approach in Web engineering is that the models specify sort of contract the Web application adheres to and promises to deliver. Similarly, in RESTful scenario, mashup components responsible for delivering composite functionalities out of RESTful components could benefit from such contracts in search, automatic mashup, and other scenarios. Such scenarios ground the need for taking RESTful Web services in existing Web methods. This paper proposes the Application Facade Component Model in existing Web methods to support RESTful, resource-oriented architectures generation. Amazon Simple Storage Service is used as the running example and proof of concept to show advantages of such approach.

NeoIDL: A Domain-Specific Language for Specifying REST Services

Proceedings of the 27th International Conference on Software Engineering and Knowledge Engineering, 2015

Service-oriented computing has emerged as an effective approach for integrating business (and systems) that might spread throughout different organizations. A service is a unit of logic modularization that hides implementation details using well-defined contracts. However, existing languages for contract specification in this domain present several limitations. For instance, both WSDL and Swagger use language-independent data formats (XML and JSON) that are not suitable for specifying contracts and often lead to heavyweight specifications. Interface description languages, such as CORBA IDL and Apache Thrift, solve this issue by providing specific languages for contract specifications. Nevertheless, these languages do not target to the REST architectural style and lack support for language extensibility. In this paper we present the design and implementation of NeoIDL, an extensible domain specific language and program generator for writing REST based contracts that are further translated into service's implementations. We also describe an evaluation that suggests the rapid return on investment with respect to the design and development of NeoIDL 1 .