is new.
public interface UserDataHandler
When associating an object to a key on a node using 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
Document Object Model (DOM) Level 3 Core Specification
.
| Field Summary | |
|---|---|
| static short |
NODE_ADOPTED
The node is adopted, using
Document.adoptNode().
|
| static short |
NODE_CLONED
The node is cloned, using Node.cloneNode(). |
| static short |
NODE_DELETED
The node is deleted. |
| static short |
NODE_IMPORTED
The node is imported, using
Document.importNode().
|
| static short |
NODE_RENAMED
The node is renamed, using
Document.renameNode().
|
| Method Summary | |
|---|---|
| void |
handle
(short operation,
String
key,
Object
data,
Node
src,
Node
dst) This method is called whenever the node for which this handler is registered is imported or cloned. |
| Field Detail |
|---|
static final short NODE_CLONED
static final short NODE_IMPORTED
Document.importNode().
static final short NODE_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.
static final short NODE_RENAMED
Document.renameNode().
static final short NODE_ADOPTED
Document.adoptNode().
| Method Detail |
|---|
void handle(short operation,
String key,
Object data,
Node src,
Node dst)
DOM applications must not raise exceptions in a UserDataHandler. The effect of throwing exceptions from the handler is DOM implementation dependent.