Debug an XSL Transformation

When you use the XSLT debugger to run a transformation you can control the process and inspect the state of the transformation using Enterprise Architect's debugger in combination with breakpoints. The XSLT Debugger provides Run and Step buttons. You set breakpoints by clicking in the left margin of the stylesheet.

When a step completes or a breakpoint is encountered, the context of the transformation - including any parameters to template calls - can be viewed in the Locals window (Analyzer | Locals). You can also display the Call stack (Analyzer | Call Stack) to see how the current state of the transformation was reached.

Debug the Transformation



See also


On the XML Transform diagram, right-click on the XML Transform Activity element and select the 'Debug XSL Transformation' option.

The XSLT Debugger view displays, showing the stylesheet (.xsl) file and XML document used in the transformation, which is automatically initiated. The currently executing statement in the stylesheet is highlighted.

Across the top of the view is a debugger toolbar, providing the normal debugging options to Start, Pause, Step Over, Step In, Step Out and Stop the debugging process. The final icon in the toolbar provides the option of hiding or showing the '.xml source' tab in the view. You can use these buttons to repeat and control the debugging process.

The System Output window also displays, showing the debugger progress messages on the 'XSLT Transformation' tab. (Press Ctrl+Shift+8 if the System Output window does not display.)

Error messages are directed to the Debugger window (press Alt+8). You can also use the Debugger window toolbar buttons and options to control debugging of the XSL Transformation.

Control Stack Depth Debug Toolbar


If necessary, select to display the Locals window and the Call Stack.

Click on the left margin of the XSLT Debugger stylesheet panel and set any Breakpoints you want to use to check processing.

Set Record Markers View the Call Stack View the Local Variables


Run the debugger again and examine the execution as indicated by the System Output window, Call Stack, Locals window, and any other Debugger or Execution Analysis tools you want to apply.

Debugging Execution Analyzer

Learn more