Package org.apache.xalan.xpath.dtm

Default liaison and XML parser.

See:
Description

Class Summary

DTM	**For internal use only** DTM is an XML document model expressed as a table rather than an object tree.
DTMLiaison	**For internal use only** Liaison to Document Table Model (DTM) XML parser -- the default liaison and parser that XSLTProcessor uses to perform transformations.
DTMNodeLocator	**For advanced use only**
DTMProxy	**For internal use only** DTMProxy presents a DOM Node API front-end to the DTM model.
DTMProxyMap	**For internal use only** DTMProxyMap is a quickie (as opposed to quick) implementation of the DOM's NamedNodeMap interface, intended to support DTMProxy's getAttributes() call.

Exception Summary

DTMException

**For internal use only** Simple implementation of DOMException.

Package org.apache.xalan.xpath.dtm Description

Default liaison and XML parser.

DOM (Document Object Model) is a standard interface for interacting with XML documents. Xalan-Java fully supports this interface. For large XML documents, however, this may involve considerable overhead, since Xalan-Java must create one or more Java objects for each Node in the document.

For the majority of cases -- your input and output are URLs, files, or streams, and you use the default Liaison DTMLiaison and XML parser DTM -- Xalan-Java avoids this overhead by implementing the Document Table Model (DTM), a pseudo-DOM that uses integer arrays in place of the DOM. For larger input and output trees, the performance improvements can be very significant.

To use the high performance DTMLiaison and parser, instantiate the XSLTProcessor as follows:

org.apache.xalan.xslt.XSLTProcessor xsltProc = org.apache.xalan.xslt.XSLTProcessorFactory.getProcessor();

When your provide input or write output in the form of a DOM Node, the XSLTProcessor switches to XercesLiaison and the Xerces DOM parser. You can explicitly instantiate an XSLTProcessor to use XercesLiaison and the Xerces DOM parser as follows:

org.apache.xalan.xslt.XSLTProcessor xsltProc = org.apache.xalan.xslt.XSLTProcessorFactory.getProcessor(
new org.apache.xalan.xpath.xdom.XercesLiaison());