Run/Debug configuration: XSLT

Create: Run | Edit Configurations | | XSLT

Enable the XPathView + XSLT plugin

This functionality relies on the XPathView + XSLT plugin, which is bundled and enabled in DataGrip by default. If the relevant features are not available, make sure that you did not disable the plugin.

Press Ctrl+Alt+S to open settings and then select Plugins.
Open the Installed tab, find the XPathView + XSLT plugin, and select the checkbox next to the plugin name.

This page describes the configuration-specific items as well as options that are common for all run/debug configurations. For more information about using this configuration, refer to XSLT run configurations and Debugging.

Settings tab

Item	Description
Input	Use the controls in this area to specify the XML file you want to process and the script you want to execute. XSLT Script File - in this field, specify the path to the XSLT Style Sheet file. Type the path manually or click Browse and select the desired file in the Choose XSLT File dialog that opens. Choose XML Input File - from this list, select the XML input file to be transformed. The list contains all the XML files that have been associated with the chosen Style Sheet via the File Associations functionality. To specify a file, which is not on the list, click Browse and select the desired file in the Choose XML File dialog, that opens.
Output	Use the controls in this area to configure handling of the script output. Show in Default Console - select this option to have the output displayed in the normal run console, together with any warnings and error messages from the XSLT transformer, as well as messages generated by the script, for example, by `xsl:message`. Show in Extra Console Tab - select this option to have the produced output displayed in an extra, XSLT Output, tab. This option is selected by default. Highlight Output As - select the file type to highlight the output as. Save to File - select this option to have the output saved directly to a file. In the field, specify the name of the target file. Type the path to the file manually or click Browse and select the desired file in the Choose Output File dialog, that opens. If you type the name of a file that does not exist, DataGrip will create a file and save the output to it. Open File in Editor After Execution - select this checkbox to have the file with the output opened in the editor after the script is executed successfully. Open File in Web Browser After Execution - select this checkbox to have the file with the output opened in the configured Web browser after the script is executed successfully. The specified file will be overwritten without requesting for confirmation.
Parameters	Use the controls in this area to create and manage a list of parameters to be passed to the script. Add - click this button to create a new entry. Remove - click this button to remove the selected entry from the list. Name - in this field, specify the name of the parameter. Value - in this field, specify the value of the parameter. The field is mandatory. Parameters without values are not passed to the script. Values are not assigned by default.

Item

Description

Input

Use the controls in this area to specify the XML file you want to process and the script you want to execute.

XSLT Script File - in this field, specify the path to the XSLT Style Sheet file. Type the path manually or click Browse and select the desired file in the Choose XSLT File dialog that opens.
Choose XML Input File - from this list, select the XML input file to be transformed. The list contains all the XML files that have been associated with the chosen Style Sheet via the File Associations functionality. To specify a file, which is not on the list, click Browse and select the desired file in the Choose XML File dialog, that opens.

Output

Use the controls in this area to configure handling of the script output.

Show in Default Console - select this option to have the output displayed in the normal run console, together with any warnings and error messages from the XSLT transformer, as well as messages generated by the script, for example, by xsl:message.
Show in Extra Console Tab - select this option to have the produced output displayed in an extra, XSLT Output, tab.
This option is selected by default.
Highlight Output As - select the file type to highlight the output as.
Save to File - select this option to have the output saved directly to a file. In the field, specify the name of the target file. Type the path to the file manually or click Browse and select the desired file in the Choose Output File dialog, that opens.
If you type the name of a file that does not exist, DataGrip will create a file and save the output to it.
- Open File in Editor After Execution - select this checkbox to have the file with the output opened in the editor after the script is executed successfully.
- Open File in Web Browser After Execution - select this checkbox to have the file with the output opened in the configured Web browser after the script is executed successfully.
The specified file will be overwritten without requesting for confirmation.

Parameters

Use the controls in this area to create and manage a list of parameters to be passed to the script.

Add - click this button to create a new entry.
Remove - click this button to remove the selected entry from the list.
Name - in this field, specify the name of the parameter.
Value - in this field, specify the value of the parameter.
The field is mandatory. Parameters without values are not passed to the script. Values are not assigned by default.

Advanced tab

In this tab, configure additional options that are not commonly required in run configurations.

Item	Description
Smart Error Handling	Clear this checkbox to have the console display full error messages including their complete stack traces, when an error occurs during execution. Select this checkbox to suppress showing stack trace and have the console display only the relevant information about errors.
VM Arguments	In this field, specify optional VM arguments to be passed to the VM where the XSLT script is executed. These can be heap size, garbage collection options, file encoding, etc. If the line of VM arguments is too long, click to expand the field and type the text there.
Working Directory	In this field, specify the working directory to use. Type the path manually or click Browse and select the desired folder in the Working Directory dialog, that opens. If no folder is specified in field, the working directory will be the one where the XSLT script file is located.

Item

Description

Smart Error Handling

Clear this checkbox to have the console display full error messages including their complete stack traces, when an error occurs during execution.
Select this checkbox to suppress showing stack trace and have the console display only the relevant information about errors.

VM Arguments

In this field, specify optional VM arguments to be passed to the VM where the XSLT script is executed. These can be heap size, garbage collection options, file encoding, etc. If the line of VM arguments is too long, click to expand the field and type the text there.

Working Directory

In this field, specify the working directory to use. Type the path manually or click Browse and select the desired folder in the Working Directory dialog, that opens.

If no folder is specified in field, the working directory will be the one where the XSLT script file is located.

Common settings

When you edit a run configuration (but not a run configuration template), you can specify the following options:

Item	Description
Name	Specify a name for the run configuration to quickly identify it among others when editing or running.
Allow multiple instances	Allow running multiple instances of this run configuration in parallel. By default, it is disabled, and when you start this configuration while another instance is still running, DataGrip suggests stopping the running instance and starting another one. This is helpful when a run configuration consumes a lot of resources and there is no good reason to run multiple instances.
Store as project file	Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project. By default, it is disabled, and DataGrip stores run configuration settings in .idea/workspace.xml.

Item

Description

Name

Specify a name for the run configuration to quickly identify it among others when editing or running.

Allow multiple instances

Allow running multiple instances of this run configuration in parallel.

By default, it is disabled, and when you start this configuration while another instance is still running, DataGrip suggests stopping the running instance and starting another one. This is helpful when a run configuration consumes a lot of resources and there is no good reason to run multiple instances.

Store as project file

Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project.

By default, it is disabled, and DataGrip stores run configuration settings in .idea/workspace.xml.

Before launch

In this area, you can specify tasks to be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.

Item	Shortcut	Description
	`Alt+Insert`	Click this icon to add one of the following available tasks: Launch Web Browser: select this option to have a browser started. In the dialog that opens, select the type of the browser and provide the start URL. Also, specify if you want the browser to be launched with the JavaScript debugger. Run External tool: select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in DataGrip yet, add its definition. For more information, refer to External tools and External Tools. Run Another Configuration: select to execute another run/debug configuration and wait until it finishes before starting the current configuration. If you want to run several configurations in parallel, use a compound run/debug configuration. Disconnect Data Source: select this option if you want to disrupt the connection to a data source before the run/debug configuration is run.
	`Alt+Delete`	Click this icon to remove the selected task from the list.
	`Enter`	Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
	`Alt+Up` `Alt+Down`	Click these icons to move the selected task one line up or down in the list. The tasks are performed in the order that they appear in the list.
Show this page		Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.
Activate tool window		By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration. Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing `Alt+4` or `Alt+5`.
Focus tool window		Select this checkbox to automatically move focus to the Run or the Debug tool window when you start the run/debug configuration.

Logs

The following options are related to logging the execution of this configuration. For more information, refer to .

Item	Description
Specify logs to be shown in the console	Specify which log files to display while running the application. Click to add a new log. In the Edit Log Files Aliases dialog, configure the following: Alias: The name of the tab where the log will be displayed. Log File Location: Specify the path to the log file or an Ant pattern. If several files of a rolling log match the pattern, DataGrip will display the most recent one. Show all files coverable by pattern: Show all logs that match the pattern. For logs in the table, you can configure the following options: Is Active: Display the specified log file. Skip Content: Do not display old log messages from previous runs.
Save console output to file	Save the console output to the specified location. Type the path manually or click the browse button and point to the desired location in the dialog that opens.
Show console when a message is printed to stdout	Activate the console when the application writes to the standard output stream.
Show console when a message is printed to stderr	Activate the console when the application writes to the standard error stream.

08 October 2024