pdk.flow.xml.XmlDOMImplementation

contains functions to operate with XML DOMImplementation variables

This functions are based on Java org.w3c.dom package classes.

https://docs.oracle.com/en/java/javase/11/docs/api/java.xml/org/w3c/dom/package-summary.html

You can always rely on Java documentation and examples!

All functions

createDocument

Creates a DOM Document object of the specified type with its document element. Note that based on the DocumentType given to create the document, the implementation may instantiate specialized Document objects that support additional features than the "Core", such as "HTML" [DOM Level 2 HTML] . On the other hand, setting the DocumentType after the document was created makes this very unlikely to happen.

Arguments:

Result:

  • output :: pdk.net.xml.Document - A new Document object with its document element. If the namespaceURI, qualifiedName, and doctype are null, the returned Document is empty with no document element.

Possible exceptions:

  • NullPointerException - throws if the domImplementation NULL

  • DOMException - INVALID_CHARACTER_ERR: Raised if the specified qualified name is not an XML name according to [XML 1.0]. NAMESPACE_ERR: Raised if the qualifiedName is malformed, if the qualifiedName has a prefix and the namespaceURI is null, or if the qualifiedName is null and the namespaceURI is different from null, or if the qualifiedName has a prefix that is "xml" and the namespaceURI is different from " http://www.w3.org/XML/1998/namespace" [XML Namespaces] , or if the DOM implementation does not support the "XML" feature but a non-null namespace URI was provided, since namespaces were defined by XML. WRONG_DOCUMENT_ERR: Raised if doctype has already been used with a different document or was created from a different implementation. NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML 4.01]).

createDocumentType

Creates an empty DocumentType node. Entity declarations and notations are not made available. Entity reference expansions and default attribute additions do not occur.

Arguments:

Result:

Possible exceptions:

  • NullPointerException - throws if the domImplementation NULL

  • DOMException - INVALID_CHARACTER_ERR: Raised if the specified qualified name is not an XML name according to [XML 1.0]. NAMESPACE_ERR: Raised if the qualifiedName is malformed. NOT_SUPPORTED_ERR: May be raised if the implementation does not support the feature "XML" and the language exposed through the Document does not support XML Namespaces (such as [HTML 4.01])

getFeature

This method returns a specialized object which implements the specialized APIs of the specified feature and version, as specified in DOM Features. The specialized object may also be obtained by using binding-specific casting methods but is not necessarily expected to, as discussed in.

Arguments:

  • domImplementation :: pdk.net.xml.DOMImplementation - The dom implementation

  • feature :: pdk.core.String - The name of the feature requested. Note that any plus sign "+" prepended to the name of the feature will be ignored since it is not significant in the context of this function

  • version :: pdk.core.String - This is the version number of the feature to test

Result:

  • output :: pdk.core.Any - Returns an object which implements the specialized APIs of the specified feature and version, if any, or null if there is no object which implements interfaces associated with that feature.

Possible exceptions:

hasFeature

Test if the DOM implementation implements a specific feature and version, as specified in DOM Features.

Arguments:

Result:

  • output :: pdk.core.Boolean - true if the feature is implemented in the specified version, false otherwise.

Possible exceptions:

Previouspdk.flow.xml.XmlDOMConfigurationNextpdk.flow.xml.XmlProcessingInstruction

Last updated