Editing XSLT stylesheets

<oXygen/> provides special support for developing XSLT 1.0 / 2.0 stylesheets.

 Validating XSLT stylesheets

Validation of XSLT stylesheets documents is performed with the help of an XSLT processor configurable from user preferences according to the XSLT version: 1.0 or 2.0. For XSLT 1.0 the options are: Xalan, Saxon 6.5.5, Saxon 9 B, Saxon 9 SA, MSXML 4.0, MSXML.NET, a JAXP transformer specified by the main Java class. For XSLT 2.0 the options are: Saxon 9 B, Saxon 9 SA, a JAXP transformer specified by the main Java class.

The Validate toolbar provides a button Validation options for quick access to the XSLT options in the <oXygen/> user preferences.

 Custom validation of XSLT stylesheets

If you need to validate an XSLT stylesheet with other validation engine than the built-in ones you have the possibility to configure external engines as custom XSLT validation engines in <oXygen/>. After such a custom validator is properly configured in Preferences it can be applied on the current document with just one click on the Custom Validation Engines toolbar. The document is validated against the schema declared in the document.

There are two validators configured by default:

MSXML 4.0

included in <oXygen/> (Windows edition). It is associated to the XSL Editor type in Preferences.

MSXML.NET

included in <oXygen/> (Windows edition). It is associated to the XSL Editor type in Preferences.

 Associate a validation scenario

Validation of XSLT stylesheets documents can be also performed through a validation scenario. To define a validation scenario first open the Configure Validation Scenario dialog. You do this with the Configure Validation Scenario action available on the menu DocumentValidate and on the Validate toolbar. .

You can validate a XSLT document using the engine from transformation scenario or a custom validation scenario. If you choose to validate using the engine from transformation scenario, and a transformation scenario is not associated with the current document or the engine has no validation support, the default engine set in OptionsPreferences+XML+XSLT/FO/XQuery+XSLT will be used. The list of reusable scenarios for documents of the same type as the current document is displayed in case you choose to use a custom validation scenario, see more in Validation Scenario section.