SOAP Message XML Data Exposure via Character Data Embedding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing SOAP message systems require recompiling intermediary systems and recipients to expose new data, limiting the ability to transmit additional information without discretely defining data fields, which is inefficient and cumbersome.
Innovation Solution
Embedding XML documents within SOAP messages as character data, allowing for the transmission of data without parsing by intermediary systems, thus enabling the exposure of new data without recompiling intermediary systems or updating all recipients.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If new data fields are added to SOAP messages, then data exposure capability is improved, but intermediary systems require recompilation which increases system complexity and maintenance burden
Solution Approach 1:
The patent embeds an XML document within the SOAP message body, creating a nested structure where the inner XML document carries the data payload. This nesting approach allows new data to be added within the embedded XML without affecting the outer SOAP message structure or requiring changes to intermediary systems that process the SOAP envelope.
Solution Approach 2:
The embedded XML document acts as a mediator that carries new data fields without requiring intermediary SOAP processing systems to be aware of or adapted to these new fields. The intermediary systems simply pass through the embedded XML content without parsing or validating its internal structure, thus avoiding the need for recompilation.
2Reliability
If data fields are discretely defined in SOAP messages, then data structure is improved, but adding new data requires updates to every recipient which reduces flexibility
Solution Approach 1:
The patent segments the data structure into two parts: the SOAP message envelope with its discrete, typed fields for reliable data exchange, and an embedded XML document that contains flexible, unstructured data. This segmentation allows the reliable SOAP protocol to maintain its structured approach while the embedded XML provides flexibility for new data types without requiring protocol changes.
Solution Approach 2:
The embedded XML document provides a dynamic data container that can accommodate new data fields, elements, and structures without requiring changes to the SOAP message definition or recipient systems. The XML's inherent flexibility allows the data structure to evolve dynamically while the SOAP envelope remains stable.
3Measurement precision
If XML documents are transmitted as parsed data in SOAP messages, then data validation is improved, but parsing overhead increases processing time
Solution Approach 1:
The patent extracts the data validation function from the SOAP message processing pipeline by placing the data in an embedded XML document that is not parsed by SOAP intermediaries. The validation occurs only at the endpoints (sender and receiver) that have the capability and need to validate the XML content, while intermediary systems simply transport the data without parsing overhead.
Data Source
AI summary
In some embodiments, a method of providing data comprises receiving an XML document. The XML document includes data from a data repository. A SOAP message is generated. The SOAP message is configured to receive a value associated with a selected one of a name-value pair and an XML attribute and configured to receive XML text. The XML document is embedded as the value within the SOAP message. The XML document is designated in the SOAP message as character data such that a SOAP parser does not parse the XML document.