Bureaucrats, editor, reviewer, Administrators
13,554
edits
Changes
Jump to navigation
Jump to search
If Saxon is found in the Java classpath, <code>XSLT 2.0</code> is used. Otherwise, Java’s internal <code>XSLT 1.0</code> implementation is used to do the transformation.<br />
→xslt:transform
|-
| valign='top' | '''Summary'''
|Transforms the document specified by <code>$input</code>, using the XSLT template specified by <code>$stylesheet</code>, and returns the result as <code>node()</code> instance. If Saxon is found in the Java classpath, <code>XSLT 2.0</code> is applied; otherwise, Java’s internal <code>XSLT 1.0</code> Xalan implementation is used. <code>$input</code> and <code>$stylesheet</code> can be specified as<br />
* <code>xs:string</code>, containing the path to the document,
* <code>xs:string</code>, containing the document in its string representation, or
* <code>element(xslt:parameters)</code>: <code><xslt:parameters/></code> must be used as root element, and the parameters are specified as child nodes, with the element name representing the key and the text node representing the value:<br /><code><xslt:parameters><br/> <xslt:key1>value1</xslt:key1><br/> ...<br/></xslt:parameters></code>
* [[Map_Functions|map structure]]: all parameters can be directly represented as key/value pairs:<br /><code>map { "key1" := "value1", ... </code>}<br/>This variant is more compact, and it facilitates the binding of arbitrary data types. Note that only strings are supported when using Saxon (XSLT 2.0). Next, the map structures are not part of the XQuery language yet, as the standardization is still in progress.
|}
