Home >
Online Product Documentation >
Table of Contents >
Scenario Properties Processor Tab (XQuery)
Scenario Properties Processor Tab (XQuery)
|
|
|
XQuery support is available only in Stylus Studio XML Professional Edition.
|
By default, Stylus Studio uses its own processor when processing XQuery. You use the
Processor tab of the
Scenario Properties dialog box to specify a different processor.
|
Tip
|
|
To take advantage of XQuery debugging, use the built-in Stylus Studio XQuery processor.
|
You can display the
Scenario Properties dialog box from the XQuery editor
XQuery Source tab or
Mapper tab. Click the
Browse button (
) at the top of the editor, or select Create Scenario from the scenario drop-down list.
Fields
Existing Scenarios
Lists the scenarios that are defined for the current XQuery. To view the processor settings for a given scenario, click the name of the scenario.
Processors supporting debugging
The processors in this group box support XQuery debugging and backmapping.
Built-in processor
The Stylus Studio built-in processor. Supports debugging and backmapping.
Saxon 8.1.1
The Saxon 8 processor. Debugging and backmapped are not enabled for this processor.
External processor
Use this field if you want to use an external XQuery processor. You must also specify the port on which you want Stylus Studio to listen for messages coming from the XQuery processor.
Other Processors
The processors in this group box do not support XQuery debugging and backmapping.
Mark Logic
Allows you to select the Mark Logic XQuery processor, and to specify (using the
Server Settings button) the information required to connect to the Mark Logic Content Interaction Server that contains the XML documents against which you want to run the XQuery.
Custom processor
Allows you to use a custom processor. Backmapping and debugging features are not supported for custom processors.
Command line
Command line for executing an external XQuery processor you define. The command line must show where to use the three arguments:
%1 is the XML source file,
%2 is the XQuery,
%3 is the result document. For example:
myXQprocessor -style %2 -source %1 -out %3, or
myXQprocessor %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.
For More Information
Creating an XQuery Scenario