Using A Standard Api To Parse Response Tag Elements - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Junos 10.3 Junos XML Management Protocol Guide
50
</interface-information>
</rpc-reply>
For more information about the
tag elements, see "Requesting Operational Information" on page 62. For a summary of
operational response tag elements, see the Junos XML API Operational Reference.
Configuration Information Responses
Configuration information responses are responses to requests for information about the
device's current configuration. The Junos XML API defines a tag element for every container
and leaf statement in the configuration hierarchy.
The following sample response includes the information at the
hierarchy level in the configuration hierarchy. For brevity, the sample shows only one user
defined at this level.
<rpc-reply xmlns:junos="URL">
<configuration>
<system>
<login>
<user>
<name>admin</name>
<full-name>Administrator</full-name>
<!-- other data tag elements for the admin user -->
</user>
</login>
</system>
</configuration>
</rpc-reply>
Configuration Change Responses
Configuration change responses are responses to requests that change the state or
contents of the device configuration. For commit operations, the Junos XML protocol
server encloses an explicit indicator of success or failure within the
tag element:
<rpc-reply xmlns:junos="URL">
<commit-results>
<!-- tag elements for information about the commit -->
</commit-results>
</rpc-reply>
For other operations, the Junos XML protocol server indicates success by returning an
opening and closing
<rpc-reply>
of emitting an explicit success indicator:
<rpc-reply xmlns:junos="URL">
</rpc-reply>
For more information, see "Changing Configuration Information" on page 103 and
"Committing a Configuration" on page 133. For a summary of the available configuration
tag elements, see the Junos XML API Configuration Reference.

Using a Standard API to Parse Response Tag Elements

Client applications can handle incoming XML tag elements by feeding them to a parser
that implements a standard API such as the Document Object Model (DOM) or Simple
attribute and contents of operational response
xmlns
tag with nothing between them, instead
</rpc-reply>
Copyright © 2010, Juniper Networks, Inc.
[edit system login]
<commit-results>