Working with the XSLT/XQuery Debugger

The following topics are present about how to follow XSLT/XQuery processing and detect errors in your stylesheets or XQuery documents:

Steps in a typical debug process

To debug a stylesheet or XQuery document follow the procedure:

  1. Open the source XML document and the XSLT/XQuery document.

  2. If you are in the <oXygen/> XML perspective switch to the <oXygen/> XSLT Debugger perspective in case of XSLT debugging or to the <oXygen/> XQuery Debugger in case of XQuery debugging with one of the actions (here explained for XSLT):

    • WindowOpen PerspectiveOther ...+<oXygen/> XSLT Debugger

    • The toolbar button Debug scenario . This action initializes the Debugger perspective with the parameters of the transformation scenario. Any modification applied to the scenario parameters (the transformer engine, the XSLT parameters, the transformer extensions, etc) will be saved back in the scenario when exiting from the Debugger perspective.

  3. Select the source XML document in the XML source selector of the Control toolbar In case of XQuery debugging if your XQuery document has no implicit source set the source selector value to NONE.

  4. Select the XSL/XQuery document in the XSL/XQuery selector of the Control toolbar.

  5. Set XSLT/XQuery parameters from the button available on the Control toolbar.

  6. Set one or more breakpoints.

  7. Step through the stylesheet using the buttons available on the Control toolbar: Step into, Step over, Step out, Run, Run to cursor, Run to end, Pause, Stop

  8. Examine the information in the Information Views to find the bug in the transformation process.

Note

Initially only the two available Saxon XSLT/XQuery Processors are active in the Debugger perspective. If you select Xalan XSLT Processor an warning message is shown requiring Xalan version 2.7.1. To set Xalan 2.7.1 you need to copy xalan.jar and serializerOxygen.jar from [oxygen]/lib and put it to the endorsed folder from your JRE/JDK used for running Eclipse (you can find it in HelpAbout Eclipse Platform+Configuration Detailsjava.endorsed.dirs entry) and restart Eclipse.