blob: 25cdd09de464eb54d6adc2b39d5422db16137ac3 [file] [log] [blame]
<?xml version="1.0" standalone="no"?>
<!DOCTYPE s1 SYSTEM "../../style/dtd/document.dtd">
<s1 title="&xslt4j; DTM">
<li><link anchor="intro">Introduction</link></li>
<li><link anchor="settings">Performance settings</link></li>
</ul><anchor name="intro"/>
<s2 title="Introduction">
<p>The Document Table Model (DTM) is an interface to a Document Model designed specifically for the needs of our XPath and XSLT
implementations. The motivation behind this model is to optimize performance and minimize storage.</p>
<p>Specifically, DTM avoids the overhead of instantiating the objects the standard DOM requires to represent a tree of nodes.
DTM uses unique integer "handles" to identify nodes, integer ID values to represent URLs, local names, and expanded names, and
integer index and length references to a string buffer to represent the text value of each node.</p>
<p>In general, the "read" APIs to DTM resemble those of the W3C Document Object Model (<resource-ref idref="dom"/>) interface.
However, in place of the DOM object tree of nodes, DTM uses integer arrays and string pools to represent the structure and content
of the XML document to be transformed. DTM also structures the document's contents slightly differently, to better match the XPath
data model; some details and constraints present in a standard DOM are suppressed, and a few XPath-specific features are added.</p>
<p>DTM is intended to be a read-only model, and so does not attempt to replicate the DOM's write or create-node operations.</p>
<p>The details of constructing a DTM vary depending on which implementation of this API you are using. Two reference implementations are
currently available:</p>
<li>SAX2DTM (built via a SAX stream)</li>
<li>DOM2DTM (which provides DTM access to an existing DOM)</li>
<p>Both DTMs can be built incrementally (see <link anchor="incremental">incremental transforms</link>). When operating incrementally, the
DTM allows the Xalan processor to begin reading the DTM and performing the transformation while the DTM is still being assembled
(for example, while the parser is still parsing the XML source), and attempts to do only as much work as is needed to support the
read requests actually made by the XPath or XSLT processor.</p>
<p>For the convenience of user-written extensions, a proxy mechanism presents the contents of the DTM as a read-only subset of the DOM.</p>
</s2><anchor name="settings"/>
<s2 title="DTM performance settings">
<p>&xslt4j; implements two DTM performance features that you can control with the TransformerFactory
<jump href="apidocs/javax/xml/transform/TransformerFactory.html#setAttribute(java.lang.String, java.lang.Object)">setAttribute(String name, Object value)</jump>
<th>Attribute name (URL)</th>
<th>Default setting</th>
<td><link anchor="incremental">incremental transforms</link></td>
<td><link anchor="optimized">optimized transforms</link></td>
<p>Both of these DTM settings are described below.</p>
<anchor name="incremental"/>
<s3 title="">
<p>Set this feature to true to enable incremental transformations. If set to false (the default), the transform and the parse
are performed on the same thread.</p>
<note> When set to true: If the parser is Xerces, we perform an
incremental transform on a single thread using the Xerces
"parse on demand" feature. If the parser is not Xerces, we run the
transform in one thread and the parse in another. Exception: if the
parser is not Xerces and the XML source is a DOMSource, setting this
feature to true has no effect.</note>
<p>Example: setting incremental transforms to true:</p>
<source>javax.xml.transform.TransformerFactory tFactory =
// setAttribute() takes a String and an Object.
</s3><anchor name="optimized"/>
<s3 title="">
<p>When set to true (the default), this feature enables optimizations that may involve structural rewrites of the stylesheet.
Any tool that requires direct access to the stylesheet structure should set this feature to false.</p>