Node.setUserData() the application can provide a handler
that gets called when the node the object is associated to is being
cloned, imported, or renamed. This can be used by the application to
implement various behaviors regarding the data it associates to the DOM
nodes. This interface defines that handler.
See also the Document Object Model (DOM) Level 3 Core Specification.
DOM - Level 3| Field Summary | ||
|---|---|---|
| public static final short | NODE_CLONED | The node is cloned, using Node.cloneNode(). |
| public static final short | NODE_IMPORTED | The node is imported, using Document.importNode(). |
| public static final short | NODE_DELETED | The node is deleted.
Note: This may not be supported or may not be reliable in certain environments, such as Java, where the implementation has no real control over when objects are actually deleted. |
| public static final short | NODE_RENAMED | The node is renamed, using Document.renameNode(). |
| public static final short | NODE_ADOPTED | The node is adopted, using Document.adoptNode(). |
| Method from org.w3c.dom.UserDataHandler Summary: |
|---|
| handle |
| Method from org.w3c.dom.UserDataHandler Detail: |
|---|
DOM applications must not raise exceptions in a UserDataHandler. The effect of throwing exceptions from
the handler is DOM implementation dependent. |