JAX-RPC Web Services Runtime Architecture for Protocol Interoperability
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current web service implementations are incomplete and lack stability, failing to provide a comprehensive platform for application integration and interoperability across diverse technologies and protocols.
Innovation Solution
The implementation of a web services architecture using JAX-RPC allows for invoking web services from a Java client application, supporting multiple transports, message formats, security standards, and dispatch models, enabling pluggability and integration with various components and protocols like HTTP, SMTP, and JMS, while providing a thin client and supporting synchronous and asynchronous processing.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If web services architecture is implemented using JAX-RPC to enable interoperability and integration across diverse technologies and protocols, then adaptability and versatility are improved, but device complexity increases
Solution Approach 1:
The patent introduces a service endpoint interface and runtime architecture that acts as an intermediary layer between diverse web service protocols and the underlying implementation. This mediator handles protocol translation, message formatting, and dispatch routing, enabling interoperability across HTTP, SMTP, JMS and other protocols without requiring complex point-to-point integrations between all protocol pairs.
Solution Approach 2:
The service endpoint interface is designed as a universal component that can handle multiple transport protocols, message formats, and dispatch models through a single standardized API. The runtime architecture provides multi-functional capabilities including synchronous and asynchronous processing, security management, and transaction coordination through unified interfaces that work across different protocols and platforms.
2Reliability
If a complete and stable web services implementation is provided to ensure reliability, then reliability is improved, but device complexity increases
Solution Approach 1:
The patent segments the web services implementation into distinct modular components including the service endpoint interface, runtime architecture, protocol adapters, and message handling layers. Each component has a specific responsibility and can be independently implemented, tested, and maintained. This segmentation provides stability through well-defined interfaces while managing complexity by breaking down the overall system into manageable pieces.
Solution Approach 2:
The runtime architecture implements self-service mechanisms for service discovery, dynamic binding, and automatic error handling. The system automatically manages service endpoint registration, message routing, and transaction coordination without requiring manual configuration for each interaction, thereby ensuring reliable operation while reducing the operational complexity burden.
3Adaptability or versatility
If support for multiple transports and message formats is added to improve adaptability, then adaptability is improved, but device complexity increases
Solution Approach 1:
The service endpoint interface serves as a mediator that abstracts away the complexity of multiple transport protocols and message formats. It provides a unified interface for sending and receiving messages while the runtime architecture handles the protocol-specific details including HTTP, SMTP, JMS, and other transports, as well as XML, JSON, and other message formats, thereby enabling multi-protocol support without proportionally increasing the complexity at the application layer.
Data Source
AI summary
A runtime architecture for web services utilizes a container driver to accept an invoke request for web services, such as from a protocol adapter. The container driver performs any necessary data binding and unbinding required to process the invoke request and associated message context, utilizing an appropriate plugin component. An interceptor receives the context information from the container driver and modifies the message context for web service compatibility. An invocation handler receives the formatted context information from the container driver and passes parameters from the message context to the target of the request. The invocation handler processes values returned from the target and passes these values to the container driver. The container driver can then formulate a response to the invoke request, and return the response and message context to the client or protocol adapter.