Class PMRDocumentImpl
- All Implemented Interfaces:
PMRDocument, Document, Node
- Direct Known Subclasses:
AbstractCMLDocumentImpl
Document interface represents the entire HTML or XML
document. Conceptually, it is the root of the document tree, and provides
the primary access to the document's data.
Since elements, text nodes, comments, processing instructions, etc.
cannot exist outside the context of a Document, the
Document interface also contains the factory methods needed
to create these objects. The Node objects created have a
ownerDocument attribute which associates them with the
Document within whose context they were created.
- Since:
- 1.0
- Author:
- Silvere Martin-Michiellot, Gemini AI (Google DeepMind)
-
Field Summary
Fields inherited from class PMRNodeImpl
childNodes, delegateNode, parentNode, pmrDocument, siblingNodesFields inherited from interface Node
ATTRIBUTE_NODE, CDATA_SECTION_NODE, COMMENT_NODE, DOCUMENT_FRAGMENT_NODE, DOCUMENT_NODE, DOCUMENT_POSITION_CONTAINED_BY, DOCUMENT_POSITION_CONTAINS, DOCUMENT_POSITION_DISCONNECTED, DOCUMENT_POSITION_FOLLOWING, DOCUMENT_POSITION_IMPLEMENTATION_SPECIFIC, DOCUMENT_POSITION_PRECEDING, DOCUMENT_TYPE_NODE, ELEMENT_NODE, ENTITY_NODE, ENTITY_REFERENCE_NODE, NOTATION_NODE, PROCESSING_INSTRUCTION_NODE, TEXT_NODE -
Constructor Summary
ConstructorsModifierConstructorDescriptionprotectedprotectedPMRDocumentImpl(PMRDocumentImpl oldPmrDoc) PMRDocumentImpl(Document document) -
Method Summary
Modifier and TypeMethodDescriptionAttempts to adopt a node from another document to this document.createAttribute(String name) Creates anAttrof the given name.createAttributeNS(String s, String t) createCDATASection(String data) Creates aCDATASectionnode whose value is the specified string.createComment(String data) Creates aCommentnode given the specified string.Creates an emptyDocumentFragmentobject.createElement(String tagName) Creates an element of the type specified.createElementNS(String s, String t) createEntityReference(String name) Creates an EntityReference object.createProcessingInstruction(String target, String data) Creates aProcessingInstructionnode given the specified name and data strings.createTextNode(String data) Creates aTextnode given the specified string.The Document Type Declaration (seeDocumentType) associated with this document.This is a convenience attribute that allows direct access to the child node that is the root element of the document.The location of the document ornullif undefined or if theDocumentwas created usingDOMImplementation.createDocument.The configuration used whenDocument.normalizeDocument()is invoked.getElementById(String id) very crudegetElementsByTagName(String name) Returns aNodeListof all theElements with a given tag name in the order in which they would be encountered in a preorder traversal of theDocumenttree.TheDOMImplementationobject that handles this document.An attribute specifying the encoding used for this document at the time of the parsing.booleanAn attribute specifying whether error checking is enforced or not.An attribute specifying, as part of the XML declaration, the encoding of this document.booleanAn attribute specifying, as part of the XML declaration, whether this document is standalone.An attribute specifying, as part of the XML declaration, the version number of this document.importNode(Node node, boolean deepCopy) hopefully supported nowstatic voidvoidThis method acts as if the document was going through a save and load cycle, putting the document in a "normal" form.renameNode(Node n, String namespaceURI, String qualifiedName) Rename an existing node of typeELEMENT_NODEorATTRIBUTE_NODE.voidsetDocumentURI(String documentURI) The location of the document ornullif undefined or if theDocumentwas created usingDOMImplementation.createDocument.voidsetStrictErrorChecking(boolean strictErrorChecking) An attribute specifying whether error checking is enforced or not.voidsetXmlStandalone(boolean xmlStandalone) An attribute specifying, as part of the XML declaration, whether this document is standalone.voidsetXmlVersion(String xmlVersion) An attribute specifying, as part of the XML declaration, the version number of this document.static voidtest()static voidtoString()//////////////////////////////////////////////////////////Methods inherited from class PMRNodeImpl
appendChild, cloneNode, compareDocumentPosition, getAttributes, getBaseURI, getChildNodes, getDelegateNode, getDelegateParentNode, getFeature, getFirstChild, getLastChild, getLocalName, getNamespaceURI, getNextSibling, getNodeName, getNodeType, getNodeValue, getOwnerDocument, getParentNode, getPrefix, getPreviousSibling, getTextContent, getUserData, hasAttributes, hasChildNodes, insertBefore, isDefaultNamespace, isEqualNode, isSameNode, isSupported, lookupNamespaceURI, lookupPrefix, normalize, removeChild, replaceChild, setDelegateNode, setNodeValue, setOwnerDocument, setOwnerDocumentRecursively, setPrefix, setTextContent, setUserData, wrapRecursivelyMethods inherited from class Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, waitMethods inherited from interface Node
appendChild, cloneNode, compareDocumentPosition, getAttributes, getBaseURI, getChildNodes, getFeature, getFirstChild, getLastChild, getLocalName, getNamespaceURI, getNextSibling, getNodeName, getNodeType, getNodeValue, getOwnerDocument, getParentNode, getPrefix, getPreviousSibling, getTextContent, getUserData, hasAttributes, hasChildNodes, insertBefore, isDefaultNamespace, isEqualNode, isSameNode, isSupported, lookupNamespaceURI, lookupPrefix, normalize, removeChild, replaceChild, setNodeValue, setPrefix, setTextContent, setUserData
-
Constructor Details
-
PMRDocumentImpl
protected PMRDocumentImpl() -
PMRDocumentImpl
-
PMRDocumentImpl
-
-
Method Details
-
getDoctype
The Document Type Declaration (seeDocumentType) associated with this document. For HTML documents as well as XML documents without a document type declaration this returnsnull. The DOM Level 1 does not support editing the Document Type Declaration, thereforedocTypecannot be altered in any way.- Specified by:
getDoctypein interfaceDocument
-
getImplementation
TheDOMImplementationobject that handles this document. A DOM application may use objects from multiple implementations.- Specified by:
getImplementationin interfaceDocument
-
getDocumentElement
This is a convenience attribute that allows direct access to the child node that is the root element of the document. For HTML documents, this is the element with the tagName "HTML".- Specified by:
getDocumentElementin interfaceDocument
-
createElement
Creates an element of the type specified. Note that the instance returned implements the Element interface, so attributes can be specified directly on the returned object.- Specified by:
createElementin interfaceDocument- Parameters:
tagName- The name of the element type to instantiate. For XML, this is case-sensitive. For HTML, thetagNameparameter may be provided in any case, but it must be mapped to the canonical uppercase form by the DOM implementation.- Returns:
- A new
Elementobject. - Throws:
DOMException- INVALID_CHARACTER_ERR: Raised if the specified name contains an invalid character.
-
createDocumentFragment
Creates an emptyDocumentFragmentobject.- Specified by:
createDocumentFragmentin interfaceDocument- Returns:
- A new
DocumentFragment.
-
createTextNode
Creates aTextnode given the specified string.- Specified by:
createTextNodein interfaceDocument- Parameters:
data- The data for the node.- Returns:
- The new
Textobject.
-
createComment
Creates aCommentnode given the specified string.- Specified by:
createCommentin interfaceDocument- Parameters:
data- The data for the node.- Returns:
- The new
Commentobject.
-
createCDATASection
Creates aCDATASectionnode whose value is the specified string.- Specified by:
createCDATASectionin interfaceDocument- Parameters:
data- The data for theCDATASectioncontents.- Returns:
- The new
CDATASectionobject. - Throws:
DOMException- NOT_SUPPORTED_ERR: Raised if this document is an HTML document.
-
createProcessingInstruction
public ProcessingInstruction createProcessingInstruction(String target, String data) throws DOMException Creates aProcessingInstructionnode given the specified name and data strings.- Specified by:
createProcessingInstructionin interfaceDocument- Parameters:
target- The target part of the processing instruction.data- The data for the node.- Returns:
- The new
ProcessingInstructionobject. - Throws:
DOMException- INVALID_CHARACTER_ERR: Raised if an invalid character is specified.
NOT_SUPPORTED_ERR: Raised if this document is an HTML document.
-
createAttribute
Creates anAttrof the given name. Note that theAttrinstance can then be set on anElementusing thesetAttributemethod.- Specified by:
createAttributein interfaceDocument- Parameters:
name- The name of the attribute.- Returns:
- A new
Attrobject. - Throws:
DOMException- INVALID_CHARACTER_ERR: Raised if the specified name contains an invalid character.
-
createEntityReference
Creates an EntityReference object.- Specified by:
createEntityReferencein interfaceDocument- Parameters:
name- The name of the entity to reference.- Returns:
- The new
EntityReferenceobject. - Throws:
DOMException- INVALID_CHARACTER_ERR: Raised if the specified name contains an invalid character.
NOT_SUPPORTED_ERR: Raised if this document is an HTML document.
-
getElementsByTagName
Returns aNodeListof all theElements with a given tag name in the order in which they would be encountered in a preorder traversal of theDocumenttree.- Specified by:
getElementsByTagNamein interfaceDocument- Parameters:
name- The name of the tag to match on. The special value "*" matches all tags.- Returns:
- A new
NodeListobject containing all the matchedElements.
-
createElementNS
- Specified by:
createElementNSin interfaceDocument
-
getElementsByTagNameNS
- Specified by:
getElementsByTagNameNSin interfaceDocument
-
importNode
hopefully supported now- Specified by:
importNodein interfaceDocument
-
createAttributeNS
- Specified by:
createAttributeNSin interfaceDocument
-
getInputEncoding
An attribute specifying the encoding used for this document at the time of the parsing. This isnullwhen it is not known, such as when theDocumentwas created in memory.- Specified by:
getInputEncodingin interfaceDocument- Since:
- DOM Level 3
-
getXmlEncoding
An attribute specifying, as part of the XML declaration, the encoding of this document. This isnullwhen unspecified or when it is not known, such as when theDocumentwas created in memory.- Specified by:
getXmlEncodingin interfaceDocument- Since:
- DOM Level 3
-
getXmlStandalone
public boolean getXmlStandalone()An attribute specifying, as part of the XML declaration, whether this document is standalone. This isfalsewhen unspecified.Note: No verification is done on the value when setting this attribute. Applications should use
Document.normalizeDocument()with the "validate" parameter to verify if the value matches the validity constraint for standalone document declaration as defined in [XML 1.0].- Specified by:
getXmlStandalonein interfaceDocument- Since:
- DOM Level 3
-
setXmlStandalone
An attribute specifying, as part of the XML declaration, whether this document is standalone. This isfalsewhen unspecified.Note: No verification is done on the value when setting this attribute. Applications should use
Document.normalizeDocument()with the "validate" parameter to verify if the value matches the validity constraint for standalone document declaration as defined in [XML 1.0].- Specified by:
setXmlStandalonein interfaceDocument- Throws:
DOMException- NOT_SUPPORTED_ERR: Raised if this document does not support the "XML" feature.- Since:
- DOM Level 3
-
getXmlVersion
An attribute specifying, as part of the XML declaration, the version number of this document. If there is no declaration and if this document supports the "XML" feature, the value is"1.0". If this document does not support the "XML" feature, the value is alwaysnull. Changing this attribute will affect methods that check for invalid characters in XML names. Application should invokeDocument.normalizeDocument()in order to check for invalid characters in theNodes that are already part of thisDocument.
DOM applications may use theDOMImplementation.hasFeature(feature, version)method with parameter values "XMLVersion" and "1.0" (respectively) to determine if an implementation supports [XML 1.0]. DOM applications may use the same method with parameter values "XMLVersion" and "1.1" (respectively) to determine if an implementation supports [XML 1.1]. In both cases, in order to support XML, an implementation must also support the "XML" feature defined in this specification.Documentobjects supporting a version of the "XMLVersion" feature must not raise aNOT_SUPPORTED_ERRexception for the same version number when usingDocument.xmlVersion.- Specified by:
getXmlVersionin interfaceDocument- Since:
- DOM Level 3
-
setXmlVersion
An attribute specifying, as part of the XML declaration, the version number of this document. If there is no declaration and if this document supports the "XML" feature, the value is"1.0". If this document does not support the "XML" feature, the value is alwaysnull. Changing this attribute will affect methods that check for invalid characters in XML names. Application should invokeDocument.normalizeDocument()in order to check for invalid characters in theNodes that are already part of thisDocument.
DOM applications may use theDOMImplementation.hasFeature(feature, version)method with parameter values "XMLVersion" and "1.0" (respectively) to determine if an implementation supports [XML 1.0]. DOM applications may use the same method with parameter values "XMLVersion" and "1.1" (respectively) to determine if an implementation supports [XML 1.1]. In both cases, in order to support XML, an implementation must also support the "XML" feature defined in this specification.Documentobjects supporting a version of the "XMLVersion" feature must not raise aNOT_SUPPORTED_ERRexception for the same version number when usingDocument.xmlVersion.- Specified by:
setXmlVersionin interfaceDocument- Throws:
DOMException- NOT_SUPPORTED_ERR: Raised if the version is set to a value that is not supported by thisDocumentor if this document does not support the "XML" feature.- Since:
- DOM Level 3
-
getStrictErrorChecking
public boolean getStrictErrorChecking()An attribute specifying whether error checking is enforced or not. When set tofalse, the implementation is free to not test every possible error case normally defined on DOM operations, and not raise anyDOMExceptionon DOM operations or report errors while usingDocument.normalizeDocument(). In case of error, the behavior is undefined. This attribute istrueby default.- Specified by:
getStrictErrorCheckingin interfaceDocument- Since:
- DOM Level 3
-
setStrictErrorChecking
public void setStrictErrorChecking(boolean strictErrorChecking) An attribute specifying whether error checking is enforced or not. When set tofalse, the implementation is free to not test every possible error case normally defined on DOM operations, and not raise anyDOMExceptionon DOM operations or report errors while usingDocument.normalizeDocument(). In case of error, the behavior is undefined. This attribute istrueby default.- Specified by:
setStrictErrorCheckingin interfaceDocument- Since:
- DOM Level 3
-
getDocumentURI
The location of the document ornullif undefined or if theDocumentwas created usingDOMImplementation.createDocument. No lexical checking is performed when setting this attribute; this could result in anullvalue returned when usingNode.baseURI.
Beware that when theDocumentsupports the feature "HTML" [DOM Level 2 HTML] , the href attribute of the HTML BASE element takes precedence over this attribute when computingNode.baseURI.- Specified by:
getDocumentURIin interfaceDocument- Since:
- DOM Level 3
-
setDocumentURI
The location of the document ornullif undefined or if theDocumentwas created usingDOMImplementation.createDocument. No lexical checking is performed when setting this attribute; this could result in anullvalue returned when usingNode.baseURI.
Beware that when theDocumentsupports the feature "HTML" [DOM Level 2 HTML] , the href attribute of the HTML BASE element takes precedence over this attribute when computingNode.baseURI.- Specified by:
setDocumentURIin interfaceDocument- Since:
- DOM Level 3
-
adoptNode
Attempts to adopt a node from another document to this document. If supported, it changes theownerDocumentof the source node, its children, as well as the attached attribute nodes if there are any. If the source node has a parent it is first removed from the child list of its parent. This effectively allows moving a subtree from one document to another (unlikeimportNode()which create a copy of the source node instead of moving it). When it fails, applications should useDocument.importNode()instead. Note that if the adopted node is already part of this document (i.e. the source and target document are the same), this method still has the effect of removing the source node from the child list of its parent, if any. The following list describes the specifics for each type of node.- ATTRIBUTE_NODE
- The
ownerElementattribute is set tonulland thespecifiedflag is set totrueon the adoptedAttr. The descendants of the sourceAttrare recursively adopted. - DOCUMENT_FRAGMENT_NODE
- The descendants of the source node are recursively adopted.
- DOCUMENT_NODE
-
Documentnodes cannot be adopted. - DOCUMENT_TYPE_NODE
-
DocumentTypenodes cannot be adopted. - ELEMENT_NODE
- Specified attribute nodes of the source element are adopted. Default attributes are discarded, though if the document being adopted into defines default attributes for this element name, those are assigned. The descendants of the source element are recursively adopted.
- ENTITY_NODE
-
Entitynodes cannot be adopted. - ENTITY_REFERENCE_NODE
- Only
the
EntityReferencenode itself is adopted, the descendants are discarded, since the source and destination documents might have defined the entity differently. If the document being imported into provides a definition for this entity name, its value is assigned. - NOTATION_NODE
Notationnodes cannot be adopted.- PROCESSING_INSTRUCTION_NODE, TEXT_NODE, CDATA_SECTION_NODE, COMMENT_NODE
- These nodes can all be adopted. No specifics.
Note: Since it does not create new nodes unlike the
Document.importNode()method, this method does not raise anINVALID_CHARACTER_ERRexception, and applications should use theDocument.normalizeDocument()method to check if an imported name is not an XML name according to the XML version in use.- Specified by:
adoptNodein interfaceDocument- Parameters:
source- The node to move into this document.- Returns:
- The adopted node, or
nullif this operation fails, such as when the source node comes from a different implementation. - Throws:
DOMException- NOT_SUPPORTED_ERR: Raised if the source node is of typeDOCUMENT,DOCUMENT_TYPE.
NO_MODIFICATION_ALLOWED_ERR: Raised when the source node is readonly.- Since:
- DOM Level 3
-
getDomConfig
The configuration used whenDocument.normalizeDocument()is invoked.- Specified by:
getDomConfigin interfaceDocument- Since:
- DOM Level 3
-
normalizeDocument
public void normalizeDocument()This method acts as if the document was going through a save and load cycle, putting the document in a "normal" form. As a consequence, this method updates the replacement tree ofEntityReferencenodes and normalizesTextnodes, as defined in the methodNode.normalize().
Otherwise, the actual result depends on the features being set on theDocument.domConfigobject and governing what operations actually take place. Noticeably this method could also make the document namespace well-formed according to the algorithm described in , check the character normalization, remove theCDATASectionnodes, etc. SeeDOMConfigurationfor details.// Keep in the document the information defined // in the XML Information Set (Java example) DOMConfiguration docConfig = myDocument.getDomConfig(); docConfig.setParameter("infoset", Boolean.TRUE); myDocument.normalizeDocument();
Mutation events, when supported, are generated to reflect the changes occurring on the document.
If errors occur during the invocation of this method, such as an attempt to update a read-only node or aNode.nodeNamecontains an invalid character according to the XML version in use, errors or warnings (DOMError.SEVERITY_ERRORorDOMError.SEVERITY_WARNING) will be reported using theDOMErrorHandlerobject associated with the "error-handler " parameter. Note this method might also report fatal errors (DOMError.SEVERITY_FATAL_ERROR) if an implementation cannot recover from an error.- Specified by:
normalizeDocumentin interfaceDocument- Since:
- DOM Level 3
-
renameNode
Rename an existing node of typeELEMENT_NODEorATTRIBUTE_NODE.
When possible this simply changes the name of the given node, otherwise this creates a new node with the specified name and replaces the existing node with the new node as described below.
If simply changing the name of the given node is not possible, the following operations are performed: a new node is created, any registered event listener is registered on the new node, any user data attached to the old node is removed from that node, the old node is removed from its parent if it has one, the children are moved to the new node, if the renamed node is anElementits attributes are moved to the new node, the new node is inserted at the position the old node used to have in its parent's child nodes list if it has one, the user data that was attached to the old node is attached to the new node.
When the node being renamed is anElementonly the specified attributes are moved, default attributes originated from the DTD are updated according to the new element name. In addition, the implementation may update default attributes from other schemas. Applications should useDocument.normalizeDocument()to guarantee these attributes are up-to-date.
When the node being renamed is anAttrthat is attached to anElement, the node is first removed from theElementattributes map. Then, once renamed, either by modifying the existing node or creating a new one as described above, it is put back.
In addition,- a user data event
NODE_RENAMEDis fired, -
when the implementation supports the feature "MutationNameEvents",
each mutation operation involved in this method fires the appropriate
event, and in the end the event {
http://www.w3.org/2001/xml-events,DOMElementNameChanged} or {http://www.w3.org/2001/xml-events,DOMAttributeNameChanged} is fired.
- Specified by:
renameNodein interfaceDocument- Parameters:
n- The node to rename.namespaceURI- The new namespace URI.qualifiedName- The new qualified name.- Returns:
- The renamed node. This is either the specified node or the new node that was created to replace the specified node.
- Throws:
DOMException- NOT_SUPPORTED_ERR: Raised when the type of the specified node is neitherELEMENT_NODEnorATTRIBUTE_NODE, or if the implementation does not support the renaming of the document element.
INVALID_CHARACTER_ERR: Raised if the new qualified name is not an XML name according to the XML version in use specified in theDocument.xmlVersionattribute.
WRONG_DOCUMENT_ERR: Raised when the specified node was created from a different document than this document.
NAMESPACE_ERR: Raised if thequalifiedNameis a malformed qualified name, if thequalifiedNamehas a prefix and thenamespaceURIisnull, or if thequalifiedNamehas a prefix that is "xml" and thenamespaceURIis different from " http://www.w3.org/XML/1998/namespace" [XML Namespaces] . Also raised, when the node being renamed is an attribute, if thequalifiedName, or its prefix, is "xmlns" and thenamespaceURIis different from "http://www.w3.org/2000/xmlns/".- Since:
- DOM Level 3
- a user data event
-
getElementById
very crude- Specified by:
getElementByIdin interfaceDocument
-
toString
Description copied from class:PMRNodeImpl//////////////////////////////////////////////////////////- Overrides:
toStringin classPMRNodeImpl
-
test
-
test
-
main
-