Deleting A Hierarchy Level Or Container Object; Deleting A Configuration Object That Has An Identifier - Juniper JUNOS OS 10.3 - XML MANAGEMENT PROTOCOL GUIDE 6-30-2010 Manual

Copyright © 2010, Juniper Networks, Inc.

Deleting a Hierarchy Level or Container Object

To delete a hierarchy level and all of its children (or a container object that has children
but no identifier), a client application includes the basic tag elements or configuration
statements for its parent levels, as described in "Creating, Modifying, or Deleting
Configuration Elements" on page 109.
If using Junos XML tag elements, the application includes the
in the empty tag that represents the level or container object:
<configuration>
<!-- opening tag for each parent level -->
<level-or-object delete="delete"/>
<!-- closing tag for each parent level -->
</configuration>
If using formatted ASCII text, the application places the
level to be removed, which is followed by a semicolon (even though in the existing
configuration it is followed by curly braces that enclose its child statements):
<configuration-text>
/* statements for parent levels */
delete:
object-or-level;
/* closing braces for parent levels */
</configuration-text>
The following example shows how to remove the
from the candidate configuration:
Client Application
<rpc>
<load-configuration>
<configuration>
<protocols>
<ospf delete="delete"/>
</protocols>
</configuration>
</load-configuration>
</r pc>

Deleting a Configuration Object That Has an Identifier

To delete a configuration object that has an identifier, a client application includes the
basic tag elements or configuration statements for its parent levels, as described in
"Creating, Modifying, or Deleting Configuration Elements" on page 109.
Chapter 5: Changing Configuration Information
delete:
[edit protocols ospf]
Junos XML Protocol Server
<rpc-reply xmlns:junos="URL ">
<load-configuration-results>
<load-success/>
</load-configuration-results>
</r pc-reply>
attribute
delete="delete"
statement above the
hierarchy level
117