Starting and Exiting a Debugging Session  

By calling up the XSLT debugger, you can follow up exactly the execution of the XSL transformation in debugging mode. To start a debugging session, you must first set at least one breakpoint in the examined XSLT program. Afterwards, call up the XSLT transformation either using the test environment or from an ABAP program using the CALL TRANSFORMATION statement.

Contrary to the ABAP Debugger, you cannot start the XSLT Debugger directly.

Prerequisites

·         The XSLT program to be examined is available as an active version.

·         The XML document is specified as transformation source either through the SOURCE addition in CALL TRANSFORMATION or through an upload within the test environment.

Procedure

Starting the Debugging Session

1.       Choose the XSLT program to be examined using transaction SE80 and start the Transformation Editor.

2.       Position the cursor in the line where you wish to set a breakpoint.

3.       Click the  icon in the application toolbar.

4.       Either start the test environment for the XSLT transformation or the respective ABAP program in which the transformation to be tested is called using CALL TRANSFORMATION.

You have started the XSLT debugger and can now control the remaining procedure using the different debugging functions.

Exiting the Debugging Session

To exit a debugging session, there is no explicit exit function available. To close the Debugger at any particular point, certain minor preparations must be made.

Proceed as follows:

1.       Delete all breakpoints that follow after the currently executed line in the XSLT program.

2.       Choose  Continue on the application toolbar.

Transformation execution is now closed and any existing result is output. The system releases all the required resources in the debugging mode.