Breakpoints
By explicitly creating a breakpoint for the XSLT program, you can call the XSLT debugger and thus start the execution of the XSL transformation in debugging mode. This is done by placing one or several breakpoints in the source code of the XSLT program. A breakpoint is therefore a signal in the XSLT program that instructs the XSLT processor to interrupt execution at a certain position in the XSL source code. The XSLT debugger is activated only when this position is reached.
Note that breakpoints cannot be set in the XML document, but only always in the source code of the XSLT program.
In the XSLT debugger, there are the following three breakpoint variants:
|
Variant |
Description |
|
Line breakpoint |
Interrupts the execution of the transformation immediately before the first executable statement of the line is called. A line breakpoint is uniquely identified in an XSLT program by the line number. Line breakpoints can be created either in the XSLT editor or in the debugger. The breakpoint line is marked yellow in the XSLT program display. |
|
Template breakpoint |
Interrupts transformation execution immediately before a template is called. To identify the template breakpoint, enter the name of the template. The corresponding breakpoint line is not highlighted in color, contrary to the line breakpoint. |
|
Program breakpoint |
Interrupts the execution of the transformation when the XSLT program is started. Program breakpoints are identified solely by the name of the XSLT program and are created in the XSLT editor. |
Whenever you explicitly save breakpoints, these are active not only for the current debugging session. They remain for the duration of an entire system session until they are deleted explicitly. Such breakpoints are often known as session breakpoints.
Activities
Creating Breakpoints Saving Breakpoints Deleting Breakpoints