org.apache.xml.dtm.ref
Class DTMNodeProxy.DTMNodeProxyImplementation
java.lang.Object
org.apache.xml.dtm.ref.DTMNodeProxy.DTMNodeProxyImplementation
- All Implemented Interfaces:
- org.w3c.dom.DOMImplementation
- Enclosing class:
- DTMNodeProxy
- static class DTMNodeProxy.DTMNodeProxyImplementation
- extends Object
- implements org.w3c.dom.DOMImplementation
Inner class to support getDOMImplementation.
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
DTMNodeProxy.DTMNodeProxyImplementation
DTMNodeProxy.DTMNodeProxyImplementation()
createDocumentType
public org.w3c.dom.DocumentType createDocumentType(String qualifiedName,
String publicId,
String systemId)
- Specified by:
createDocumentType
in interface org.w3c.dom.DOMImplementation
createDocument
public org.w3c.dom.Document createDocument(String namespaceURI,
String qualfiedName,
org.w3c.dom.DocumentType doctype)
- Specified by:
createDocument
in interface org.w3c.dom.DOMImplementation
hasFeature
public boolean hasFeature(String feature,
String version)
- Ask whether we support a given DOM feature.
In fact, we do not _fully_ support any DOM feature -- we're a
read-only subset -- so arguably we should always return false.
On the other hand, it may be more practically useful to return
true and simply treat the whole DOM as read-only, failing on the
methods we can't support. I'm not sure which would be more useful
to the caller.
- Specified by:
hasFeature
in interface org.w3c.dom.DOMImplementation