Echelon LonBridg Server - Manual (Page 32)

26 LonBridge API
Examples:
Error deleting non-existing object:
<lon _tt="54321">
<o73.delete/>
<o77.delete/>
</lon>
...
<lon _tt="54321">
<error description="Object does not exist" code="1">
<o73.delete/>
</error>
</lon>
...
<lon>
<core2.lon1.o77.is_deleted/>
</lon>
More complex error reporting:
<lon>
<o90.turnon/>
<o73.delete/>
</lon>
...
<lon>
<error description="Method does not exist on this object"
code="6">
<o90.turnon/>
</error>
</lon>
...
<lon>
<error description="Object does not exist" code="1">
<o73.delete/>
</error>
</lon>
Parsing a LonBridge XML Message
To parse a LonBridge XML message, a LonBridge application can use a XML
parser or a custom parsing routine. For example, you could base a parsing
routine on the following ECMAScript function:
function parse_node(name) {
p = name.split('.');
if (p.length > 4) {
return null;
}
var properties = new Array("domain", "client", "object",
"method");
o = {domain: null, client: null, method: null,
object: null};
posProperty = 3;
for(i = p.length - 1; i >= 0; i--) {
o[properties[posProperty]] =
p[i] != null && p[i].length > 0) p[i] : null;