Home >Online Product Documentation >Table of Contents >Scenario Properties Used for Generating Code
Scenario Properties Used for Generating Code
When you generate code for XSLT, Stylus Studio uses some of the information associated with the active XSLT scenario, as specified in the Scenario Properties dialog box.
The following tables summarizes the scenario properties that affect code generation.
Tab
|
Comment
|
|---|
General
|
The Code Generation wizard uses only the Source XML URL and the Output URL field, if specified. All other properties on this page are ignored.
|
Processor
|
You can use the following XSLT processors for generating Java code:
l Saxon
l Java built-in
If the Stylus Studio URI Resolver property is selected, the generated code includes lines that import and register ConverterFactory and ConverterResolver classes from DataDirect XML Converters.
Note: If the scenario specifies an XSLT processor for which Java code generation is not supported, Stylus Studio uses the Java built-in processor for code generation purposes. The processor specified in the scenario is not changed.
|
Parameter Values
|
By default, parameter values are treated as a literal string. If you prefer to have parameter values treated as XPath expressions in the generated code, check the Parameter value is an XPath expression (not a string) checkbox.
|
Profiling Options
|
Ignored.
|
Validation
|
You can use the following validation engines for validating your XSLT Java code:
l Saxon
l Java built-in
If you choose a validation engine that is not supported, Stylus Studio uses the Java built-in validation engine.
|
Post-process
|
Only post-processing using Apache FOP and RenderX XEP is specified in the generated code. Resulting PDF is written to the output URL specified on the General tab.
|
Table 64. Scenario Properties that Affect Code Generation
Cart
