Processor Settings (XSLT)

You use the Processor Settings page of the Options dialog box to specify default settings for XSLT processors, and to specify which processor you want to use as the default processor in your XSLT scenarios. You can always select a different processor and override individual settings on the Processor tab of the Scenario Properties dialog box.

Fields

Processor

Drop-down list that displays available processors for XSLT. The debugging symbol changes based on whether or not the processor you have selected supports back-mapping and debugging. The following table summarizes the available processors and whether or not they support back-mapping and debugging.

Table 198. Available XSLT Processors
Processor	Supports Back-mapping and Debugging
Built-in	Yes
Saxon 9.x	Yes
Java built-in	No
.NET XslTransform	Yes
.NET XslCompiledTransform	No
Microsoft MSXML	No
Microsoft MSXML 4	No
Microsoft MSXML 6	No
Custom	No

Use Stylus Studio URI Resolver

Whether or not you want to enable the Stylus Studio URI Resolver, which allows the processor to resolve URIs associated with file systems peculiar to Stylus Studio (like the file system for XML conversions, for example). This setting is applicable only to Java-based processors such as Saxon.

Use a default processor

Whether or not you want use the processor you are configuring as the default processor for all XSLT scenarios. You can always override the default processor and individual processor settings on the Processor tab of the Scenario Properties dialog box when you create the scenario.

Custom Processor Settings

Command line, path, and pathname settings for the custom XSLT processor. These fields are available only if you select Custom from the Processor drop-down list.

Command line

The command line used to execute the custom XSLT processor. The command line must show where to use the three arguments: %1 is the XML source file, %2 is the XSLT stylesheet, %3 is the result document. For example: myparser -style %2 -source %1 -out %3, or myparser %1 %2 %3.

Path

Specifies any path information that is required to run your custom processor and that is not already defined in your PATH environment variable.

Classpath

Specifies any directories that your processor must access and that are not already defined in your CLASSPATH environment variable.