Use of array notation to build messages with repeating substructures
Permalink
Bookmark
Share
Twitter
Digg
Reddit
Facebook
Stumbleupon
Del.icio.us| IP.com Number | IPCOM000176849D |
|
|
|---|---|---|---|
| Dated | Nov 25, 2008 UTC | ||
| Size | 3 page(s) (52.8 KB) | ||
| Disclosed by |
|
||
Publication Summary
Message brokers are intermediary programs that transform route messages between applications. Most brokers allow user defined logic to be executed during the processing of a message. One such embodiment allows PHP scripts to be executed in a broker. This publication explains how the familiar PHP array syntax can be used to build messages with repeating substructures.| Country | |
|---|---|
| Language | English (United States) |
About this Publication
This document was submitted to IP.com's Prior Art Database and this preview is designed to provide you with information regarding the contents of this document by displaying up to the first four pages of the document as scaled page renderings and displaying a limited amount of text which was extracted from the document on the Text Preview Tab.
To find out more on how to obtain the entire document, click the Download tab. There is a charge for downloading some Prior Art Database documents; please examine carefully whether you believe this document fills your needs before purchasing.
For more information about the Prior Art Database, visit the Learn section of this website. Thank you for visiting IP.com's Prior Art Database! You may wish to check out our Intellectual Property Library website before you leave.
Use of array notation to build messages with repeating substructures
Message processing in a broker (or ESB) typically involves its transformation from one format to another to allow disparate applications to exchange data. The content of the input message is generally used to determine the content or destination of the output. Frequently, scripts are written in a programming language to specify the exact nature of this transformation processing. A parser is invoked by the system to translate the input message into a hierarchical (tree) structure representing the logical model of the message (e.g. DOM is a hierarchical representation of an XML document).
Current systems exist to create messages as the tree representations are being navigated. For example, the ESQL language in IBM * WebSphere * Message Broker supports the following syntax:
SET OutputRoot.XML.a.b.c = 'foo';
which will generate the following XML:
foo
The general rule is that the interpreter will attempt to navigate the tree in accordance with the path syntax, but if an element doesn't exist in the tree, then it is created. However, if we wish to create a second
element as a sibling of the existing one, there is no existing way to specify this as a new element rather than the existing one using a path syntax. For example the following code:
SET OutputRoot.XML.a.b.c = 'foo';
SET OutputRoot.XML.a.b.c = 'bar';
would generate the following XML:
bar
This changes the value of the existing
element rather than creating a new one.
Existing solutions to this would be to navigate to the element, obtain a reference (pointer) to this element and then explicitly call a function to create this second element. The proposed solution would reduce the amount of user code required to achieve the same result.
This solution proposes a mechanism for utilising the array building syntax of a scripting language to be applied to element objects enabling multiple repeating su...