A content handler can get a reference to a TransformState by implementing the TransformerClient interface.
It doesn't look like this code, which is for tooling, has functioned propery for a while, so it doesn't look like it is being used.
This interface is meant to be used by a consumer of SAX2 events produced by Xalan, and enables the consumer to get information about the state of the transform.
Class used to clone a node, possibly including its children to a result tree.
A class that does incremental counting for support of xsl:number.
This is a table of counters, keyed by ElemNumber objects, each of which has a list of Counter objects.
Structure to help in converting integers to roman numerals
This class implements an optimized iterator for "key()" patterns, matching each node to the match attribute in one or more xsl:key declarations.
This class manages the key tables.
This class filters nodes from a key iterator, according to whether or not the use value matches the ref value.
Table of element keys, keyed by document node.
This class will manage error messages, warning messages, and other types of message events.
This class can sort vectors of DOM nodes according to a select pattern.
This class acts as a base for ResultTreeHandler, and keeps queud stack events.
A representation of a result namespace.
This is a helper class that decides if Xalan needs to switch serializers, based on the first output element.
Class to guard against recursion getting too deep.
A TransformerHandler listens for SAX ContentHandler parse events and transforms them to a Result.
This class implements the
Transformer interface, and is the core
representation of the transformation execution.
Handle a walk of a tree, but screen out attributes for the result tree.
XalanProperties defines the features understood by
Before the serializer merge, the TransformState interface was implemented by ResultTreeHandler.
In charge of run-time transformations and the production of result trees.
For each node in the XML source, TransformerImpl uses the StylesheetRoot and underlying XSLT schema to determine which template to apply: one of the templates in the StylesheetRoot, a default template rule as specified in the XSLT spec, or none.
The Transformer works with
forward the SAX-like events produced by the
transformation to the appropriate output ContentHandler.
To the degree possible, the parsing of the XML source and application of the Templates object to that source are performed concurrently in separate threads. When necessary, the Transformer waits for the parse events that must be in place before a given template may be applied.
Copyright © 2012 JBoss by Red Hat. All Rights Reserved.