Dynamic Web Services Interface Model Generation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional web services modeling applications and tools fail to achieve sufficient interoperability and client-side flexibility due to limitations in web services metadata and the separation of standards, models, and entities, leading to convoluted relationships and mappings between relevant standards, which are not evolving fast enough to meet the increasing demand for web services.

Innovation Solution

A dynamic web services interface model is generated using extracted metadata from a Web Service Definition Language (WSDL) file, comprising an interface metadata and a type metadata model, allowing for the creation of a dynamic web services interface model that is independent of specific web services APIs and can consume multiple web services without the need for proxy classes, using a dynamic proxy within a core web services framework.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional web services modeling applications and tools are used with separate standards, models, and entities, then interoperability is partially achieved through open standards like XML, SOAP, WSDL, and UDDI, but client-side flexibility is insufficient and the relationships between standards become convoluted

Engineering Contradiction:

Improveclient-side flexibilityVSAvoidconvoluted relationships between standards

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent combines previously separate web services standards, models, and entities into a unified framework. The Java API for XML-based RPC (JAX-RPC) is enhanced to integrate WSDL description, data access, and object manipulation capabilities within a single cohesive system, eliminating the need for separate handling of multiple standards and reducing convoluted relationships.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The enhanced JAX-RPC framework provides universal functionality that can consume multiple web services through a common interface. The unified model supports various web services operations (search, find, engage) and handles different data formats and protocols through a single adaptable architecture, improving client-side flexibility without requiring separate specialized tools for each standard.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If JAX-RPC 1.1 metadata is used for web services description, then basic web services functionality is provided, but dynamic web services interfaces, data access, and object manipulation are not supported

Engineering Contradiction:

Improvedynamic web services interface capabilityVSAvoidweb service details hidden in metadata

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent segments the web services metadata into distinct functional components: interface description (WSDL), data access layer, and object manipulation layer. This segmentation allows each component to be independently accessed and manipulated, enabling dynamic interface generation while preserving detailed web service information that was previously hidden in consolidated metadata.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent adds a new dimension to JAX-RPC by introducing dynamic interface generation capabilities that operate at runtime. Instead of static metadata-only approaches, the system creates dynamic proxies and interfaces that can adapt to different web services, exposing detailed service information through generated code rather than hidden metadata structures.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

3Productivity

If open standards like XML, SOAP, WSDL, and UDDI are used for web services interoperability, then basic web services functionality is achieved, but the standards are not evolving fast enough to meet increasing demand for web services

Engineering Contradiction:

Improveweb services demand fulfillmentVSAvoidstandards evolution speed

Core Design Contradiction:

ProductivityVSSpeed

Solution Approach 1:

The patent implements preliminary action by pre-compiling and caching web services interfaces and metadata at runtime. The dynamic proxy generation and interface compilation processes prepare web services consumption in advance, reducing the need for repeated parsing and interpretation of WSDL and metadata, thereby increasing productivity without waiting for standards to evolve.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces dynamic capabilities that allow the web services framework to adapt and evolve independently of standard evolution. The system dynamically generates interfaces, compiles proxies, and adjusts to new web services formats and protocols in real-time, enabling rapid response to increasing web services demand without being constrained by the slower evolution pace of open standards.

Inventive Principle:

Principle #15Dynamics

Data Source

PatentUS8099709B2Method and system for generating and employing a dynamic web services interface model

Publication Date: 2012.01.17 SAP SE

AI summary

A system and method are provided to generate a dynamic web services interface model. In one embodiment, description content of a Web Service Definition Language (WSDL) file is identified. A first metadata and a second metadata are extracted from the description content. A dynamic web services interface model is created via the first metadata and the second metadata.