Web Service Middleware Dynamic Resource File Reloading

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing Web service frameworks, such as Apache XML Project and Microsoft .NET, are cumbersome and closed, respectively, which reduces developer productivity and limits the efficiency of deploying and testing Web services, particularly due to the lack of an open and extendable framework compatible with HTTP requests.

Innovation Solution

A method and system that processes client requests to identify resource files and requested actions, allowing for dynamic reloading of resource files and generating responses in the form of WSDL, HTML test pages, or XML Schema Description (XSD), while supporting HTTP GET and POST requests, thereby enhancing developer productivity and compatibility with HTTP requests.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If Apache XML Project software is used for building Web services, then Web service functionality is achieved, but developer productivity is reduced due to cumbersome operation

Engineering Contradiction:
Improveease of deploying and testing Web serviceVSAvoiddeveloper productivity
Core Design Contradiction:
Ease of operationVSProductivity

Solution Approach 1:

The system enables automatic reloading of resource files when changes are detected, eliminating the need for manual intervention or system restarts. This self-service mechanism allows the Web service framework to automatically adapt to configuration changes, thereby improving ease of operation and developer productivity without requiring complex manual deployment procedures

Inventive Principle:
Principle #25Self-service

2Adaptability or versatility

If Microsoft .NET framework is used for integrating Web services, then Web service integration is achieved, but extensibility is limited due to closed implementation

Engineering Contradiction:
ImproveextensibilityVSAvoidframework implementation structure
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system employs dynamic resource file reloading that allows the framework to adapt its configuration at runtime without requiring a complete system restart. This dynamic approach enables extensibility by allowing developers to modify and add functionalities through resource file changes, making the framework more adaptable while maintaining a manageable implementation structure

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The Web service framework is designed to handle multiple protocols including SOAP, HTTP GET, and HTTP POST requests through a unified architecture. This multi-functional design allows the same framework to serve multiple purposes and integrate with different Web service standards, thereby improving adaptability without significantly increasing implementation complexity

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If resource files are reloaded in runtime, then developer productivity is improved by eliminating restart requirement, but system complexity increases

Engineering Contradiction:
Improvedeveloper productivityVSAvoidmiddleware management complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The middleware automatically monitors for changes in resource files and performs reloading when changes are detected, without requiring manual intervention or increasing operational complexity. This self-service capability improves developer productivity by eliminating the need to restart the middleware while the automatic nature of the process prevents significant increases in system complexity

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS7587447B2Systems, methods and computer programs for implementing and accessing web services
Publication Date: 2009.09.08 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US7587447B2 patent drawing
  • US7587447B2 patent drawing
  • US7587447B2 patent drawing

AI summary

A method of responding to a request from a client to a Web service is disclosed. The method includes the steps of: a) processing the request to identify a resource file and a requested action, wherein the request is encoded in one of a plurality of protocols; b) accessing the resource file which includes data describing the Web service; c) processing the request using at least a portion of the data to produce a response; and d) returning a response to the client. A computer system is also disclosed. The computer system includes a client adapted to send a request to a Web service, and a middleware which receives the request from the client. The computer system also includes a resource file accessible to the middleware. The resource file includes data describing the Web service. The middleware identifies the resource file and requested action from the request, which is encoded in one of a plurality of protocols.