Use the XSL Transformation launch configuration

To create a launch configuration that will load an XSL transformation for debugging, do the following:

In a workbench perspective that offers the launch/debug/run action set (such as the Debug perspective), do one of the following:
• Select Run > Debug from the workbench menu bar to open the Debug launch configurations dialog box.

• Select the workbench toolbar Debug push button and choose Debug from the menu. This will open the Debug launch configurations dialog box.

In the Debug launch configurations dialog box, do one of the following:

• Select the XSL Transformation node and click New.

• Right-click the XSL Transformation node and select New from the pop-up menu.

• Double-click the XSL Transformation node.

This will cause the launch configuration tabs and entry fields to display on the right-hand side of the dialog box. In the Name field, enter a name of your choice for the configuration that you are creating. Select the Main tab to bring it to the foreground.

1. In the Main tab Project field, enter the name of the project that contains the source for the application that you wish to debug. If the application source is not in a workbench project, you can enter the name of the project that contains the application that you wish to debug, and then indicate the source search path in the launch configuration Source tab page.

   Rather than enter a project name in the Project field, you can browse for the project by clicking Browse.

   Completion of this field is optional. However, if you want to debug using source for XSLT include or import files on your workstation, the source for these files must be located in a project that is specified in this field or as a source location (in the launch configuration Source tab or in the Edit Source Lookup Path dialog).

   If you complete this field, the Browse button location for the other fields in the tab will default to the project location.

2. Enter the full path and name of the XSL file that you wish to debug in the Source XSL file field. Alternatively, you may browse for the file by clicking Browse. Completion of this field is mandatory.
3. In the Source XML file field, enter the full path and name of the XML input file for the XSL file that you wish to debug. Alternatively, you may browse for the file by clicking Browse. Completion of this field is mandatory.
4. In the Output file field, specify the name and location of your output file.
5. The Stop in first template rule check box is selected by default. With this selected, the transformation process will stop at the first template defined in the XSL file.
Click the Parameters tab. In the Parameters page, you can specify:
1. Stylesheet Parameters - Click Add to add a new stylesheet parameter Name and Value to this list. In your XSL stylesheet, you can define an xsl:param with a Name. You can use this page to specify a new Value for your parameter or override the existing one.

2. Output Properties - You can select to override the default output properties specified in your source files. Click F1 for more information about the fields.

3. Transform Properties - You can specify the Recursion limit and URI base The Recursion limit specifies how many levels you want the transformation to link to and the URI base is a context path you can set so URIs will resolve properly.
Click the JRE tab. This page defines the JRE used to run and debug the application.
1. Select the Workspace default JRE radio button if you want to use the default workspace JRE.
2. Otherwise, select the Alternate JRE radio button if you want to select from a list of already defined JREs. Click Installed JREs if you want to add another JRE to your list of options.

   Note: You will also have to specify the Java executable you want to use with the JRE you select.

Click the Classpath tab. The Classpath page defines the location of class files used when running and debugging the application. By default, the user and bootstrap class locations are derived from the associated project's build path. You may override these settings here. To set the Source Lookup Path, select the Source tab and do the following:
• To add a source location, click Add. This will invoke the Add Source dialog, which allows you to select the type of source location to add. From the selection list in the Add Source dialog, choosing Workspace will cause all projects in your workspace to be added to the source search path. All other selections that are valid for debugging XSL transformations will result in a dialog which allows you to enter or browse for the desired source search path location.

• To remove an existing entry, select a source location and click Remove.

• To set the order of existing entries, select a source location and click Up or Down to alter that location's placement.

  Note: In some cases, changing the placement of a location may not take effect until the next time the program is launched.

If you wish to search for all instances of the source filename in the source search path, select the Search for duplicate source files on the path check box. If you select this check box and the debugger finds multiple instances of the filename, you will be prompted via a dialog to choose the correct source file.

Select the Common tab to bring it to the foreground. You can do the following in the Common page:
• If you want the launch configuration to be stored locally and available for a single user, ensure that the Local radio button is selected. If the launch configuration is to be stored as a file in the workspace and shared in a repository for team use, select the Shared radio button and enter the project location where you wish the launch configuration to be stored in the Location of shared configuration field. Alternatively, you may browse for the project.

• If you would like the launch configuration to appear as a favorite debug configuration in the Debug push button favorites menu or the Debug menu Debug History list, select the Debug check box.

If all information mandatory to the launch configuration has been provided, the Debug and Apply push buttons will be enabled. Clicking Apply will save the launch configuration, at which point you can choose to close the dialog box without launching the debug session or you can click Debug to launch a debug session using the new launch configuration. If you click Debug, any changes to the launch configuration will be saved and a debug session will be launched.

After you have saved a debug launch configuration, you may edit it. For further information about editing debug launch configurations, see the related task below.

Tip: If you have not yet saved launch configuration settings and if you have made entries in the launch configuration settings that you would like to remove or change, clicking Revert will remove all changes that you have made. If information mandatory to the launch configuration has not been provided or if there are errors in the information that you have provided, messages at the top of the dialog box will indicate what is missing. If you did not use the dialog box to launch a debug session (for example, you used it instead to create and save a launch configuration), click Close to exit the dialog when you are finished working in it.

 

Related tasks

Preparing to debug
Locating source
Starting a debug session
Using the debug launch shortcuts
Creating new launch configurations from existing launch configurations
Editing launch configurations
Removing launch configurations