Unified XML Schema Java Mapping Model for Web Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web services technologies face challenges in achieving interoperability and client-side flexibility due to convoluted relationships and mappings between standards, lacking support for consumer-based approaches, and inadequate modeling for both web services and clients, which hinders usability and interoperability across diverse platforms.
Innovation Solution
A method and system for generating schema to Java™ mapping descriptors and direct mapping of XML schema and Java™ interfaces, involving the creation of customized schema to Java™ mapping information and the use of a common meta model that combines web services and web services client frameworks, eliminating the need for virtual interfaces and enabling design-time and runtime configurations, thus facilitating interoperability and flexibility.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional web services models with separate standards, models, and entities are used, then some interoperability is achieved through open standards, but client-side flexibility and usability are insufficient due to convoluted relationships and mappings
Solution Approach 1:
The patent merges the web services provider model and web services client model into a single unified model. This combines previously separate standards, models, and entities into one coherent framework, eliminating the convoluted relationships between multiple separate models and enabling both provider-oriented and consumer-based approaches within a single unified structure.
Solution Approach 2:
The unified model serves multiple functions simultaneously: it supports both provider-oriented inside-out approaches and consumer-based outside-in approaches, handles both design-time and runtime configurations, and provides a single model that works for both web services and web services clients. This multi-functionality eliminates the need for separate specialized models.
2Adaptability or versatility
If conventional STJ mappings with serializer and deserializer classes are used, then basic schema to Java mapping is achieved, but field or operation-specific mappings and design-time configurations are not supported
Solution Approach 1:
The mapping structure is segmented into distinct components: the unified model contains both runtime configurations and design-time configurations as separate but integrated elements. Field-specific and operation-specific mappings are separated as distinct configurable elements within the unified model, allowing precise control over different aspects of the mapping without creating a monolithic complex structure.
Solution Approach 2:
Design-time configurations are performed in advance using the unified model, allowing field-specific and operation-specific mappings to be predetermined before runtime. This preliminary action enables the system to have pre-configured mapping rules that simplify runtime operations while maintaining the capability for customization.
3Adaptability or versatility
If provider-oriented inside-out approach is used, then web services can be deployed, but consumer-based outside-in approach is not supported
Solution Approach 1:
The unified model is designed to be dynamic, supporting multiple approaches depending on the scenario. It can operate in provider-oriented inside-out mode when services are being deployed, and switch to consumer-based outside-in mode when clients are consuming services. This dynamic capability allows the same model to adapt to different operational contexts without requiring separate specialized models.
Data Source
AI summary
A method and system for generating schema to Java™ mapping description. In one embodiment, default schema to Java™ mapping information is customized into customized schema to Java™ mapping information. An object having the customized mapping information is created, and schema to Java™ generation is initialized via the object.