XFA Specification
Chapter 13, Dealing with Data in Different XML Formats
XSLT Transformations
400
The XFA Configuration DOM may include a
debug
element that nominates a place in which to save a copy
of the data after the XSLT transformation but before any other transformations. If the
debug
element is
supplied and is non-empty, and the XSLT transformation is performed, the data loader copies the output
of the XSLT transformation into the nominated place.
For example, the following fragment from an XFA configuration document causes the script
"massage.xslt"
to be used for preprocessing the XML data document. The preprocessed document is
copied to
"massage.xml"
before being loaded by the data loader.
<xsl>
<debug>
<uri>massage.xml</uri>
</debug>
<uri>massage.xslt</uri>
</xsl>
XSLT Postprocessing
This section describes an extended mapping rule that can be used to modify data being written to a new
XML data document under control of an XSLT script [XSLT].
The XFA Configuration DOM may include an
outputXSL
element. If present, the
outputXSL
element
must contain a
uri
element that nominates the XSLT script. See
“Config Specification” on page 676
full schema. When the
outputXSL
element is supplied, the data loader executes the script after applying
all other transformations to the data.
Note that
debug
may not be used inside
outputXSL
.
For example, an XFA Configuration DOM includes the following fragment:
<outputXSL>
<uri>out.xslt</uri>
</outputXSL>
This causes the output XML document from the data loader to be passed to an XSLT interpreter, along with
the local file
"out.xslt"
, which contains an XSLT style sheet. The style sheet supplies all required
additional configuration such as the destination of the transformed document.