REST Endpoint System for SOAP Message Pair Processing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing business applications, such as CRM and ERP, face challenges in efficiently processing and handling message pairs between clients and servers using SOAP protocol, as they require separate code for each message pair, which can be cumbersome and inefficient.
Innovation Solution
Implementing a REST endpoint system that processes request messages based on message pair data, where parameter values are extracted from either the URI or payload according to parameter binding information, allowing common code to handle various operations and entity types, and generating new message pair data for REST endpoints from existing SOAP message pairs.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate code is developed for each message pair in SOAP protocol, then each message pair can be handled specifically, but the code becomes cumbersome and inefficient
Solution Approach 1:
The patent implements a universal message processing framework that can handle multiple message pair types through a single code structure. The framework uses a message queue and standardized processing logic that works across different message types (create, read, update, delete operations), eliminating the need for separate code for each message pair while maintaining reliable handling.
Solution Approach 2:
The patent introduces a message queue as an intermediary component between message reception and processing. This queue standardizes the message flow and allows a single processing code to handle various message types uniformly, reducing code complexity while maintaining reliable message pair handling through the standardized intermediary layer.
2Productivity
If common code is used to process message pairs, then code duplication is reduced, but separate code was originally required for each message pair
Solution Approach 1:
The patent creates a universal message processing code that handles all message pair types through standardized operations. The common code uses a message queue and generic processing logic that adapts to different message types (create, read, update, delete), improving development efficiency while maintaining processing accuracy through the standardized universal approach.
Solution Approach 2:
The patent uses parameter-based message identification where the common code processes messages by extracting and responding to specific parameters within the message structure. This allows a single code to handle multiple message types reliably by changing parameters rather than requiring separate code paths, improving both productivity and reliability.
3Loss of information
If SOAP protocol is used for client-server communication, then structured information exchange is enabled, but the protocol requires complex message pair handling
Solution Approach 1:
The patent introduces a message queue as an intermediary that simplifies SOAP protocol message handling. The queue standardizes the flow of structured information between client and server, reducing the complexity of message pair processing while maintaining complete information exchange through the organized intermediary layer.
Solution Approach 2:
The patent segments the message processing into distinct phases: message reception, queue insertion, and standardized processing. This segmentation of the SOAP protocol handling reduces complexity by breaking down the complex message pair processing into manageable, standardized steps that can be handled by common code.
Data Source
AI summary
An endpoint system provides a REST endpoint for an application. The endpoint system processes request messages based on message pair data for each message that includes an operation and parameter data. The parameter data includes parameter information for each parameter that identifies whether the value for the parameter is to be taken from the URI or payload of a request message. The endpoint system receives request messages that have a URI and payload. The URI includes an operation name. The endpoint system processes each request message in accordance with the message pair data for the operation specified in the request message. For each parameter of the message pair data, the endpoint system extracts the value for the parameter from either the URI or payload as specified by the parameter information for the parameter. The endpoint system then invokes the operation passing the one or more extracted values as actual parameters.