Altova XMLSpy 2022 Enterprise Edition

The XSL section (screenshot below) enables you to define options for XSLT transformations and XSL-FO transformations carried out from within the application.



XSLT transformations

XMLSpy contains the Altova RaptorXML XSLT 1.0, XSLT 2.0, and XSLT 3.0 engines, which you can use for XSLT transformations as well as for validating the XML files used in transformations. The appropriate XSLT engine (1.0, 2.0, or 3.0) is used (according to the value of the version attribute  of the xsl:stylesheet or xsl:transform element). This applies both for XSLT transformations as well as for XSLT debugging using XMLSpy's XSLT/XQuery Debugger.


For transforming XML documents using XSLT, you could use one of the following:


The built-in Altova XSLT Engines (XSLT 1.0, XSLT 2.0, and XSLT 3.0).

The MSXML 3.0, 4.0, or 6.0 parser (which is pre-installed). If you know which version of the MSXML parser is running on your machine, you could select it; otherwise, you should let the application select the version automatically. (The Choose version automatically option is active by default.) In this case, the application tries to select the most recent available version.

An external XSLT processor of your choice. You must specify the command line string that the external XSLT processor uses to run a transformation. The following variables are available for building the command line string:


%1        = XML document to process

%2        = Output file to generate

%3        = XSLT stylesheet to use (if the XML document does not contain a reference to a stylesheet)


For example, say you have a processor that uses the following command to run an XSLT transformation:


myxsltengine.exe -o output.xml input.xml stylesheet.xslt parameter-name=parameter-value


Then, in XMLSpy, you can use the variables listed above to generate this command. Select the External XSL Transformation Program radio button, and enter the following line in the text box:


c:\myxsltengine\myxsltengine.exe -o %2 %1 %3 parameter-name=parameter-value


Check the respective check boxes to show the output and error messags of the external program in the Messages Window in XMLSpy.


Note:The parameters set in XMLSpy's XSLT Input Parameters dialog are passed to the internal Altova XSLT Engines only. They are not passed to any other XSLT Engine that is set up as the default XSLT processor.


The Reuse output window option causes subsequent transformations to display the result document in the same output window. If the XML file belongs to a project and Reuse output window option is disabled, the setting only takes effect if the Save in folder output file path (screenshot below) in the relevant project properties is also disabled.



XSL-FO transformations

FO documents are processed using an FO processor, and the path to the executable of the FO processor must be specified in the text box for the XSL-FO transformation engine. The transformation is carried out using the XSL/XQuery | XSL-FO Transformation menu command. If the source file (the active document when the command is executed in the IDE) is an XSL-FO document, the FO processor is invoked for the transformation. If the source document is an XML document, an XSLT transformation is required to first convert the XML document to an XSL-FO document. This XSLT transformation can be carried out either by the XSLT engine you have specified as the default engine for the application (see above), or by the XSLT engine that might be built into the FO processor you have specified as the default FO processor for the application. To select between these two options, click the appropriate radio button.


After making the settings, click OK to finish.


Note:Unless you deselected the option to install the FOP processor of the Apache XML Project, it will have been installed in the folder C:\ProgramData\Altova\SharedBetweenVersions. If installed, the path to it will automatically have been entered in the XSL-FO Engine input box. You can set the path to any FO processor you wish to use. Note, however, that the same path will be used by other Altova products that use FO processors and have settings to select the FO processor (StyleVision and Authentic Desktop).


Save and exit

After making the settings, click OK to finish.



© 2016-2022 Altova GmbH