The Debugger perspective interface looks like below. This interface is comprised of 4 panes as follows:
Displays and allows editing of data or document oriented XML files (documents).
Displays and allows editing of XSL files(stylesheets) or XQuery documents.
Displays the transformed output that results from the input of a selected document (XML) and selected stylesheet (XSL) or XQuery document to the transformer. The result of transformation is dynamically written as the transformation is processed.
The control view provides functionality for configuration and control of debugging operations. It also provides a series of Information views types. This pane is comprised of two parts:
XML documents and XSL stylesheets or XQuery documents that were opened in Editor perspective are automatically sorted into the first two panes. When multiple files of each type are opened, the individual documents and stylesheets are separated using the familiar tab management system of the Editor perspective. Selecting a tab brings the document or stylesheet into focus and enables editing without toggling back to the Editor perspective.
During debugging the current execution node is highlighted on both document (XML) and XSL/XQuery views.
The toolbar contains all actions needed in order to configure and control the debug process. Items are described below from left to right as they appear in the toolbar.
The selection represents the source document to be used as input by the transformation engine. The selection list is filled-in with all opened files (the XML ones being emphasized). This gives you the possibility to use other file types as source. In case of XQuery debugging session this selection field can be set to default value NONE, as usually XQuery documents do not require an input source.
The selection represents the stylesheet or XQuery document to be used by the transformation engine. The selection list is filled-in with all opened files (the XSL/XQuery ones being emphasized).
Lists the available XSLT/XQuery processors
(Saxon and Xalan Java - see specifications for XSLT or Saxon9B for XQuery.)
XSLT/XQuery parameters to be used by the transformation.
Add and remove the Java classes and jars used as XSLT extensions.
Enable/Disable current transformation profiling.
Enable or disable rendering of output to the XHTML Output document View during the transformation process. For performance issues, it is advisable to disable XHTML output for large jobs. Also, the XHTML area is only able to render XHTML documents. In order to view the output result of other formats, such as HTML, save the Text output area to a file and use the required external browser for viewing.
When starting a debug session from the editor perspective using the Debug Scenario action, the state of this toolbar button reflects the state of the "Show as XHTML" output option from the scenario.
Starts the debugging process and runs until the next stylesheet node (next step in transformation).
Executes the current stylesheet node (including its sub-elements) and goes to next node in document order (usually the next sibling of the current node).
Steps out to the parent node (equivalent to the Step over (F8) on the parent).
Starts the debugging process and runs until the first breakpoint is encountered or until the end of transformation occurs, if no breakpoints are encountered (see the section called “Breakpoints View”).
Starts the debugging process and runs until one of the following conditions occur: the line of cursor is reached, a valid breakpoint is reached or end of execution.
Runs the transformation until the end, without taking into account any enabled breakpoints that might be set.
Interrupts the current transformation. This is useful for long transformations (DocBook for instance) when you want to find out what point the transformation has reached. The transformation can be resumed after.
Ends the transformation process.