System and method for processing messages using native data serialization/deserialization in a service-oriented pipeline architecture
US-9195527-B2 · Nov 24, 2015 · US
US9852116B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9852116-B2 |
| Application number | US-201514919193-A |
| Country | US |
| Kind code | B2 |
| Filing date | Oct 21, 2015 |
| Priority date | Sep 30, 2008 |
| Publication date | Dec 26, 2017 |
| Grant date | Dec 26, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A computer-implemented system and method for processing messages using native data serialization/deserialization without any transformation, in a service-oriented pipeline architecture is disclosed. The method in an example embodiment that includes serializing or deserializing the request/response message directly into the format (specific on-the-wire data format or a java object) the recipient expects (either a service implementation or a service consumer or the framework), without first converting into an intermediate format. This provides an efficient mechanism for the same service implementation to be accessed by exchanging messages using different data formats.
Opening claim text (preview).
What is claimed is: 1. A method comprising: determining a data format of a received message, the data format being a first data format, activating, among a plurality of data format parsers for a plurality of respective data formats, a data format parser corresponding to the determined data format of the received message; using the activated data format parser, operating on the received message to make the received message resemble a second data format different from the first data format; and using an unmarshaller specific to the second data format and implemented by a hardware processor, unmarshalling the received message resembling the second data format. 2. The method of claim 1 , wherein the unmarshaller is a Java Architecture for XML Binding (JAXB) unmarshaller, the second format is Extensible Markup Language (XML), and the first format is a format other than XML, the unmarshalling comprising converting the received message into Java objects. 3. The method of claim 2 , wherein the data format parsers are Streaming API for XML (Stax) parsers. 4. The method of claim 2 , wherein the first data format is a binary format. 5. The method of claim 2 , wherein the first data format is name value (NV) format. 6. The method of claim 2 , wherein the first data format is Java Script Object Notation (JSON) format. 7. The method of claim 1 , wherein the received message is a request message received from a client. 8. The method of claim 1 , further comprising transmitting the unmarshalled received message to a service implementation. 9. The method of claim 1 , wherein the determination of the data format of the received message is made by the unmarshaller. 10. The method of claim 1 , wherein the data format parsers are pluggable. 11. A system comprising: an unmarshaller implemented using a hardware processor and configured to: unmarshall messages having or resembling a first data format; determine, upon receipt of a message, that a data format of the received message is of a second data format different from the first data format; and activate, among a plurality of data format parsers for a plurality of respective data formats, a particular data format parser corresponding to the second data format of the received message in response to the second data format being different from the first data format; and the plurality of data format parsers, the particular data format parser configured to operate, upon activation by the unmarshaller, on the received message to make the received message resemble the first data format. 12. The system of claim 11 , wherein the first data format is XML and the unmarshaller is a Java Architecture for XML Binding (JAXB) unmarshaller configured to convert messages resembling XML into Java objects. 13. The system of claim 11 , wherein the data format parsers are Streaming API for XML (Stax) parsers. 14. The system of claim 11 , wherein plurality of data format parsers include at least one of a data format parser for NV format, a data format parser for binary format, or a data format parser for JSON format. 15. The system of claim 11 , wherein the unmarshaller is configured to cause transmission of the unmarshalled message to a service implementation. 16. The system of claim 11 , wherein the data format parsers are pluggable. 17. A machine-readable medium storing sets of processor-executable instructions, the sets of instructions comprising: instructions to unmarshall messages having or resembling a first data format; for each of a plurality of other data formats different from the first data format, a data format parser that includes instructions to operate on other messages having one of the other data formats to make the other messages resemble the first data format; instructions to determine that a data format of a received message is one of the other data formats; instructions to cause, in response to determining that the received message is one of the other data formats, execution of a respective data format parser that includes respective instructions for the determined other data format to make the received message resemble the first data format; and instructions to cause execution of the instructions to unmarshall messages having or resembling the first data format with respect to the received message that has been made to resemble the first data format. 18. The machine-readable medium of claim 17 , wherein the instructions to unmarshall include instructions to convert the message to Java objects. 19. The machine-readable medium of claim 17 , wherein the first data format is XML. 20. The machine-readable medium of claim 17 , wherein the instructions to unmarshall, when executed by a processor, implement a JAXB unmarshaller.
Parsing markup language streams (streaming G06F40/149) · CPC title
based on web technology, e.g. hypertext transfer protocol [HTTP] · CPC title
Adaptation of the text data for streaming purposes, e.g. Efficient XML Interchange [EXI] format · CPC title
Transformation · CPC title
via adapters, e.g. between incompatible applications · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.