Debugging Java extensions called from XSL transformations

If your XSL transformation calls a Java™ extension, you can step into the Java extension call by completing the steps in this page.
  1. Set a breakpoint on the line in the XSLT stylesheet that calls the Java extension. Alternatively, step to this line.
  2. When the line is reached, issue a step into. This will cause the debugger to stop on the first executable line of the Java method that is called (as long as the class is not filtered for stepping - for information about stepping through the execution of a Java program, see the Java development tools (JDT) debugger documentation). Both the XSLT and Java stack frames will be displayed in the Debug view. The top Java stack frame will be selected and you can inspect the Java source and variables.
  3. Click on the XSLT stack frame that called the Java extension and, if you want, inspect the XSLT source and variables. You can then step in the Java method and use typical Java debugging features (as if you were debugging a Java application). For information about debugging Java, see the Java development tools (JDT) debugger documentation.
  4. To return to the calling XSLT stack frame, issue a step return from the Java method.

An alternative method for debugging a Java extension called from XSLT is to set a breakpoint in the Java method and then run to the breakpoint.

To debug XSL that calls Java, you launch an XSL transformation debug session. For information about launching an XSL transformation debug session, see Starting a debug session.

Related concepts
XSLT debugger
Related tasks
Using the Debug view
Stepping through a program
Terminating a debug session
Running XSL transformations during a debug session
Debugging Java extensions called from XSL transformations
Debugging XSLT called from Java
Using step-by-step debugging when debugging XSLT

Feedback