Updating Applications on Application Servers
When running or debugging a Java EE or Web application, you can modify the source code and, almost immediately, see the result of your changes.
- Updating an application: Process overview
- Specifying application update options
- Updating an application
- Application update options
Updating an application: Process overview
- Specify the necessary application update options in your server run/debug configuration, see Specifying application update options.
- Start the run/debug configuration.
- After making changes to the source code, update your application, see Updating an application.
Specifying application update options
On 'Update' action.
The Update action refers to clicking
in the Run or the Debug tool window
(alternatively, Ctrl+F10 or
Use the list to select the default update option. See Application update options.
Show dialog. If this check box is not selected, the default update option is used. Otherwise, a dialog is shown that displays all the available update options, and you'll be able to select the necessary option prior to actually updating your application.
- On frame deactivation. Frame deactivation means switching from IntelliJ IDEA to a different application (e.g. a Web browser). Use the list to specify what IntelliJ IDEA should do in such cases.
Updating an application
If the necessary update option is associated with frame deactivation, your application is updated automatically when you switch from IntelliJ IDEA to a different application (e.g. a Web browser).
You can also update your application in the Application Servers Tool Window by redeploying your application artifact ().
Application update options
The update options are different depending on:
- the artifact format, i.e. on whether the application artifact is exploded (unpacked) or packed (e.g. WAR, EAR)
- the run/debug configuration type, i.e. on whether the run/debug configuration is local or remote (see Local and remote run configurations)