delete

<delete> is used:

A response to <delete> should be a <status> indicating whether or not the <delete> was processed successfully.

Example

<delete class-name="User" src-dn="\Sam">
<association>1012</association>
</delete>

1. Allowed Content

association
Unique key of the application object.
operation-data
Operation additional custom data.
driver-operation-data
Operation additional custom data used by the drivershim.

2. Attributes

AttributeValue(s)Default Value
cached-time CDATA
The time the event was placed into the driver cache. The format is CCYYMMDDhhmmss.mmmZ, always in UTC.
#IMPLIED
class-name CDATA
The name of the base class of the object.
The class name is mapped between the application and eDirectory name spaces by the schema mapping rule so that DirXML will see the name in the eDirectory namespace and a driver will see the name in the application name space.
#IMPLIED
dest-dn CDATA
The distinguished name of the target object in the namespace of the receiver.

Should be left empty for event notifications.
#IMPLIED
dest-entry-id CDATA
The entry id of the target object in the namespace of the receiver.

Should be left empty for event notifications.
#IMPLIED
event-id CDATA
An identifier used to tag the results of an event or command.
#IMPLIED
qualified-src-dn CDATA
The qualified version of src-dn. Only used for describing objects from eDirectory.
#IMPLIED
src-dn CDATA
The distinguished name of source object that generated the event in the namespace of the sender.
#IMPLIED
src-entry-id CDATA
The entry id of source object that generated the event in the namespace of the sender.

(Reserved) Should be ignored by the driver.
#IMPLIED
timestamp CDATA
(Reserved) Should be ignored by the driver.
#IMPLIED

3. Content Rule

( association ? , operation-data ? , driver-operation-data ? )

4. Parent Elements

input
  Input events or commands.

Top Elements || All Elements || Tree


NDS DTD