org.w3c.dom.Element interface and additionally allows
for the storage of non-textual objects via the
getUserObject and setUserObject methods.
This class is not intended to be used for general XML
processing. In particular, Element nodes created
within the Image I/O API are not compatible with those created by
Sun's standard implementation of the org.w3.dom API.
In particular, the implementation is tuned for simple uses and may
not perform well for intensive processing.
Namespaces are ignored in this implementation. The terms "tag name" and "node name" are always considered to be synonymous.
IIOMetadataNode.IIOMetadataNode with a given node
name.newChild to the end of the list of
children of this node.getParentNode returns null).
If a shallow clone is being performed (deep is
false), the new node will not have any children or
siblings. If a deep clone is being performed, the new node
will form the root of a complete cloned subtree.
The equals method implements an equivalence relation
on non-null object references:
x, x.equals(x) should return
true.
x and y, x.equals(y)
should return true if and only if
y.equals(x) returns true.
x, y, and z, if
x.equals(y) returns true and
y.equals(z) returns true, then
x.equals(z) should return true.
x and y, multiple invocations of
x.equals(y) consistently return true
or consistently return false, provided no
information used in equals comparisons on the
objects is modified.
x,
x.equals(null) should return false.
The equals method for class Object implements
the most discriminating possible equivalence relation on objects;
that is, for any non-null reference values x and
y, this method returns true if and only
if x and y refer to the same object
(x == y has the value true).
Note that it is generally necessary to override the hashCode method whenever this method is overridden, so as to maintain the general contract for the hashCode method, which states that equal objects must have equal hash codes.
getAttributeNodeNS method.Attr node by local name and namespace URI.
null as the
namespaceURI parameter for methods if they wish to have
no namespace.null as the
namespaceURI parameter for methods if they wish to have
no namespace.NodeList of all descendant Elements
with a given tag name, in document order.NodeList of all the descendant
Elements with a given local name and namespace URI in
document order.null if
the node has no children.null if
the node has no children.length-1 inclusive.getNodeName.null, since namespaces are not supported.null if
the node has no next sibling.ELEMENT_NODE.null, since IIOMetadataNodes
do not belong to any Document.null value
indicates that the node is the root of its own tree. To add a
node to an existing tree, use one of the
insertBefore, replaceChild, or
appendChild methods.null, since namespaces are not supported.null
if this node has no previous sibling.Node.localName is different
from null, this attribute is a qualified name. For
example, in:
<elementExample id="demo"> ... </elementExample> ,
tagName has the value
"elementExample". Note that this is case-preserving in
XML, as are all of the operations of the DOM. The HTML DOM returns
the tagName of an HTML element in the canonical
uppercase form, regardless of the case in the source HTML document.Object value associated with this node.true when an attribute with a given name is
specified on this element or has a default value, false
otherwise.true when an attribute with a given local name and
namespace URI is specified on this element or has a default value,
false otherwise.
null as the
namespaceURI parameter for methods if they wish to have
no namespace.true if this node has child nodes.java.util.Hashtable.
The general contract of hashCode is:
hashCode method on each of
the two objects must produce the same integer result.
As much as is reasonably practical, the hashCode method defined by class Object does return distinct integers for distinct objects. (This is typically implemented by converting the internal address of the object into an integer, but this implementation technique is not required by the JavaTM programming language.)
newChild before the existing
child node refChild. If refChild is
null, insert newChild at the end of
the list of children.false since DOM features are not
supported.indexth item in the collection. If
index is greater than or equal to the number of nodes in
the list, this returns null.IIOMetadataNodes do not
contain Text children.wait methods.
The awakened thread will not be able to proceed until the current thread relinquishes the lock on this object. The awakened thread will compete in the usual manner with any other threads that might be actively competing to synchronize on this object; for example, the awakened thread enjoys no reliable privilege or disadvantage in being the next thread to lock this object.
This method should only be called by a thread that is the owner of this object's monitor. A thread becomes the owner of the object's monitor in one of three ways:
synchronized statement
that synchronizes on the object.
Class, by executing a
synchronized static method of that class.
Only one thread at a time can own an object's monitor.
wait methods.
The awakened threads will not be able to proceed until the current thread relinquishes the lock on this object. The awakened threads will compete in the usual manner with any other threads that might be actively competing to synchronize on this object; for example, the awakened threads enjoy no reliable privilege or disadvantage in being the next thread to lock this object.
This method should only be called by a thread that is the owner
of this object's monitor. See the notify method for a
description of the ways in which a thread can become the owner of
a monitor.
Document.normalizeDocument() to guarantee this
information is up-to-date.
removeAttributeNS method.Attr node is defined in the DTD, a new node
immediately appears with the default value as well as the
corresponding namespace URI, local name, and prefix when applicable.
The implementation may handle default values from other schemas
similarly but applications should use
Document.normalizeDocument() to guarantee this
information is up-to-date.Document.normalizeDocument() to guarantee this
information is up-to-date.
null as the
namespaceURI parameter for methods if they wish to have
no namespace.oldChild from
the list of children, and returns it.oldChild with
newChild in the list of children, and returns the
oldChild node.Attr node plus any
Text and EntityReference nodes, build the
appropriate subtree, and use setAttributeNode to assign
it as the value of an attribute.
setAttributeNS method.nodeName) is already present in the element, it is
replaced by the new one. Replacing an attribute node by itself has no
effect.
setAttributeNodeNS method.null as the
namespaceURI parameter for methods if they wish to have
no namespace.qualifiedName, and
its value is changed to be the value parameter. This
value is a simple string; it is not parsed as it is being set. So any
markup (such as syntax to be recognized as an entity reference) is
treated as literal text, and needs to be appropriately escaped by the
implementation when it is written out. In order to assign an
attribute value that contains entity references, the user must create
an Attr node plus any Text and
EntityReference nodes, build the appropriate subtree,
and use setAttributeNodeNS or
setAttributeNode to assign it as the value of an
attribute.
null as the
namespaceURI parameter for methods if they wish to have
no namespace.isId is true, this method
declares the specified attribute to be a user-determined ID attribute
. This affects the value of Attr.isId and the behavior
of Document.getElementById, but does not change any
schema that may be in use, in particular this does not affect the
Attr.schemaTypeInfo of the specified Attr
node. Use the value false for the parameter
isId to undeclare an attribute for being a
user-determined ID attribute.
setIdAttributeNS method.isId is true, this method
declares the specified attribute to be a user-determined ID attribute
. This affects the value of Attr.isId and the behavior
of Document.getElementById, but does not change any
schema that may be in use, in particular this does not affect the
Attr.schemaTypeInfo of the specified Attr
node. Use the value false for the parameter
isId to undeclare an attribute for being a
user-determined ID attribute.isId is true, this method
declares the specified attribute to be a user-determined ID attribute
. This affects the value of Attr.isId and the behavior
of Document.getElementById, but does not change any
schema that may be in use, in particular this does not affect the
Attr.schemaTypeInfo of the specified Attr
node. Use the value false for the parameter
isId to undeclare an attribute for being a
user-determined ID attribute.toString method returns a string that
"textually represents" this object. The result should
be a concise but informative representation that is easy for a
person to read.
It is recommended that all subclasses override this method.
The toString method for class Object
returns a string consisting of the name of the class of which the
object is an instance, the at-sign character `@', and
the unsigned hexadecimal representation of the hash code of the
object. In other words, this method returns a string equal to the
value of:
getClass().getName() + '@' + Integer.toHexString(hashCode())
The current thread must own this object's monitor. The thread
releases ownership of this monitor and waits until another thread
notifies threads waiting on this object's monitor to wake up
either through a call to the notify method or the
notifyAll method. The thread then waits until it can
re-obtain ownership of the monitor and resumes execution.
As in the one argument version, interrupts and spurious wakeups are possible, and this method should always be used in a loop:
synchronized (obj) {
while (<condition does not hold>)
obj.wait();
... // Perform action appropriate to condition
}
This method should only be called by a thread that is the owner
of this object's monitor. See the notify method for a
description of the ways in which a thread can become the owner of
a monitor.The current thread must own this object's monitor.
This method causes the current thread (call it T) to place itself in the wait set for this object and then to relinquish any and all synchronization claims on this object. Thread T becomes disabled for thread scheduling purposes and lies dormant until one of four things happens:
A thread can also wake up without being notified, interrupted, or timing out, a so-called spurious wakeup. While this will rarely occur in practice, applications must guard against it by testing for the condition that should have caused the thread to be awakened, and continuing to wait if the condition is not satisfied. In other words, waits should always occur in loops, like this one:
synchronized (obj) {
while (<condition does not hold>)
obj.wait(timeout);
... // Perform action appropriate to condition
}
(For more information on this topic, see Section 3.2.3 in Doug Lea's
"Concurrent Programming in Java (Second Edition)" (Addison-Wesley,
2000), or Item 50 in Joshua Bloch's "Effective Java Programming
Language Guide" (Addison-Wesley, 2001).
If the current thread is interrupted by another thread while it is waiting, then an InterruptedException is thrown. This exception is not thrown until the lock status of this object has been restored as described above.
Note that the wait method, as it places the current thread into the wait set for this object, unlocks only this object; any other objects on which the current thread may be synchronized remain locked while the thread waits.
This method should only be called by a thread that is the owner
of this object's monitor. See the notify method for a
description of the ways in which a thread can become the owner of
a monitor.
This method is similar to the wait method of one
argument, but it allows finer control over the amount of time to
wait for a notification before giving up. The amount of real time,
measured in nanoseconds, is given by:
1000000*timeout+nanos
In all other respects, this method does the same thing as the method of one argument. In particular, wait(0, 0) means the same thing as wait(0).
The current thread must own this object's monitor. The thread releases ownership of this monitor and waits until either of the following two conditions has occurred:
notify method
or the notifyAll method.
timeout
milliseconds plus nanos nanoseconds arguments, has
elapsed.
The thread then waits until it can re-obtain ownership of the monitor and resumes execution.
As in the one argument version, interrupts and spurious wakeups are possible, and this method should always be used in a loop:
synchronized (obj) {
while (<condition does not hold>)
obj.wait(timeout, nanos);
... // Perform action appropriate to condition
}
This method should only be called by a thread that is the owner
of this object's monitor. See the notify method for a
description of the ways in which a thread can become the owner of
a monitor.