|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Class Summary | |
DocumentWrapper | The document node of a tree implemented as a wrapper around a DOM Document. |
DOMEmitter | DOMEmitter is an Emitter that attaches the result tree to a specified Node in a DOM Document |
DOMNodeList | This class wraps a SequenceExtent as a DOM NodeList - though this will only work if the items are nodes, and if the nodes themselves implement the DOM Node interface (which is true of the two Saxon tree models, but not necessarily of all possible implementations). |
DOMSender | DOMSender.java: pseudo-SAX driver for a DOM source document. |
DOMTransform | Variant of command line net.sf.saxon.Transform do build the source document in DOM and then proceed with the transformation. |
NamespaceNode | A node (implementing the NodeInfo interface) representing a Namespace node in the DOM wrapping interface |
NodeWrapper | A node in the XML parse tree representing an XML element, character content, or attribute. |
This package provides glue classes that enable Saxon to process a source document supplied as a DOM tree in the form of a DOMSource object).
The classes NodeWrapper and DocumentWrapper implement the Saxon interfaces NodeInfo and DocumentInfo on top of an underlying DOM Node or Document object respectively. This enables XPath expressions to be executed directly against the DOM.
Note that using the DOM with Saxon is considerably less efficient than using Saxon's native tree implementations, the Tiny Tree and the (so-called) Standard Tree. The DOM should be used only where there is some good reason, e.g. where other parts of the application have to use DOM interfaces.
Saxon doesn't stop you modifying the contents of the DOM in the course of a transformation (for example, from an extension function, or in a different thread) but the consequences of doing so are unpredictable.
New in Saxon 7.8
Michael H. Kay
4 November 2003
|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |