The
XSLT tab contains the following options:
- XML URL - Specifies the source
XML file. This URL is resolved through the catalog resolver. If the catalog does not
have a mapping for the URL, then the file is used directly from its remote
location.
Note: If the transformer
engine is Saxon 9 and a custom URI resolver is configured in
Preferences for Saxon 9, the XML input of the transformation
is passed to that URI resolver.
Note: If the
transformer engine is one of the built-in XSLT 2.0 / 3.0 engines and the name of an initial
template is specified in the scenario, the XML URL
field can be empty. The XML URL field can also be empty if you
use external XSLT processors. Otherwise, a value is mandatory in
the XML URL field.
- XSL URL - Specifies the source XSL file that the
transformation will use. This URL is resolved through the catalog resolver. If the
catalog does not have a mapping for the URL, the file is used directly from its remote
location.
The rest of the options available in the
XSLT tab allow you to further
customize the transformation scenario:
- Use "xml-stylesheet" declaration - Use the stylesheet declared
with an xml-stylesheet declaration instead of the stylesheet specified in
the XSL URL field. By default, this checkbox is not selected and
the transformation applies the XSLT stylesheet that is specified in the XSL
URL field. If it is checked, the scenario applies the stylesheet specified
explicitly in the XML document with the xml-stylesheet processing
instruction.
- Transformer - This drop-down list presents
all the transformation engines available to Oxygen XML Editor for performing a
transformation. These are the built-in engines and the external engines defined in the Custom
Engines preferences page. The engine you choose in this dialog is used as the
default transformation engine. Also, if an XSLT or XQuery document does not have an
associated validation scenario, this transformation engine is used in the validation
process (if it provides validation support).
Advanced options - Allows you to configure
the advanced options of the Saxon HE / PE / EE engine for the current transformation
scenario. To configure the same options globally, go to the Saxon-HE/PE/EE preferences page. For
the current transformation scenario, these Advanced options
override the options configured in the Saxon-HE/PE/EE preferences page. The Initial mode and
template option is only available in the Advanced
options. It is a Saxon-specific option that sets the name of the first
XSLT template that starts the XSLT transformation or the initial mode of the
transformation.
- Parameters - Opens the Configure parameters
dialog, allowing you to configure the XSLT parameters used in the current
transformation. In this dialog you can also configure the parameters of additional
stylesheets by using the Additional XSLT stylesheets button. If
the XSLT transformation engine is custom-defined, you can not use this dialog to
configure the parameters sent to the custom engine. Instead, you can copy all parameters
from the dialog using contextual menu actions and edit the custom XSLT engine to include
the necessary parameters in the command line that starts the transformation
process.
- Extensions - Opens the dialog for configuring the XSLT/XQuery
extension jars or classes that define extension Java functions or extension
XSLT elements used in the transformation.
- Additional XSLT stylesheets
- Opens the dialog for adding XSLT
stylesheets that are applied on the main stylesheet that is specified in the
XSL URL field. This is useful when a chain of XSLT stylesheets
must be applied to the input XML document.