"DOMImplementation" implementation.
* *At this writing, the following features are supported: "XML" (L1, L2), * "Events" (L2), "MutationEvents" (L2), "USER-Events" (a conformant extension), * "HTMLEvents" (L2), "UIEvents" (L2), "Traversal" (L2). It is possible to * compile the package so it doesn't support some of these features (notably, * Traversal). * * @author David Brownell * @version $Date: 2002/09/30 15:08:51 $ */ public class DomImpl implements DOMImplementation { /** * Constructs a DOMImplementation object which supports * "XML" and other DOM Level 2 features. */ public DomImpl () {} /** * DOM L1 * Returns true if the specified feature and version are * supported. Note that the case of the feature name is ignored. */ public boolean hasFeature (String name, String version) { name = name.toLowerCase (); if ("xml".equals (name) || "core".equals (name)) { if (version == null) return true; if ("1.0".equals (version)) return true; if ("2.0".equals (version)) return true; } else if ("events".equals (name) || "mutationevents".equals (name) || "uievents".equals (name) // || "mouseevents".equals (name) || "htmlevents".equals (name) ) { if (version == null) return true; if ("2.0".equals (version)) return true; // Extension: "USER-" prefix event types can // be created and passed through the DOM. } else if ("user-events".equals (name)) { if (version == null) return true; if ("0.1".equals (version)) return true; // NOTE: "hasFeature" for events is here interpreted to // mean the DOM can manufacture those sorts of events, // since actually choosing to report the events is more // often part of the environment or application. It's // only really an issue for mutation events. } else if (DomNode.reportMutations && "traversal".equals (name)) { // Note: nyet tree walker support ... if (version == null) return true; if ("2.0".equals (version)) return true; } // views // stylesheets // css, css2 // range return false; } /** * DOM L2 * Creates and returns a DocumentType, associated with this * implementation. This DocumentType can have no associated * objects (notations, entities) until the DocumentType is * first associated with a document. * *
Note that there is no implication that this DTD will * be parsed by the DOM, or ever have contents. Moreover, the * DocumentType created here can only be added to a document by * the createDocument method (below). That means that the only * portable way to create a Document object is to start parsing, * queue comment and processing instruction (PI) nodes, and then only * create a DOM Document after (a) it's known if a DocumentType * object is needed, and (b) the name and namespace of the root * element is known. Queued comment and PI nodes would then be * inserted appropriately in the document prologue, both before and * after the DTD node, and additional attributes assigned to the * root element. * (One hopes that the final DOM REC fixes this serious botch.) */ public DocumentType createDocumentType ( String rootName, String publicId, String systemId // CR2 deleted internal subset, ensuring DocumentType // is 100% useless instead of just 90% so. ) { DomDocument.verifyNamespaceName (rootName); return new DomDoctype (this, rootName, publicId, systemId, null); } /** * DOM L2 * Creates and returns a Document, populated only with a root element and * optionally a document type (if that was provided). */ public Document createDocument ( String namespaceURI, String rootName, DocumentType doctype ) { Document doc = new DomDocument (this); Element root; root = doc.createElementNS (namespaceURI, rootName); if (namespaceURI != null) { if (rootName.startsWith ("xmlns:")) throw new DomEx (DomEx.NAMESPACE_ERR, "xmlns is reserved", null, 0); root.setAttribute ("xmlns", namespaceURI); } if (doctype != null) doc.appendChild (doctype); // handles WRONG_DOCUMENT error doc.appendChild (root); return doc; } }