13.8 Detecting updates and reloading the J2EE applications

For the exploded archive-format J2EE applications, if you update the files to be configured, you can reload the updated J2EE applications. By using the reload functionality, you dynamically replace the already deployed servlets, JSPs, and EJB-JARs without restarting the J2EE server.

When you use the redeploy functionality, the procedure required for replacing a normal J2EE application, such as stopping and deleting the J2EE application before the application is replaced, and importing and deploying the replaced J2EE application, become unnecessary. As a result, the J2EE application is dynamically replaced within a few steps.

You can use the reload functionality to replace the modified J2EE applications and running J2EE applications during testing in application development and during system operations.

This section describes the detection of updates and the reloading of J2EE applications.

Note that for the applications containing cosminexus.xml, the cosminexus.xml information is not updated even if update detection and reloading is executed for J2EE applications.

The following table describes the organization of this section.

Table 13-8 Organization of this section (Detecting updates and reloading the J2EE applications)

CategoryTitleReference location
ExplanationHow to reload J2EE applications13.8.1
Scope of reloading13.8.2
Class loader configuration used for reloading13.8.3
Operations when an error occurs13.8.4
Files for update detection13.8.5
Update detection interval for J2EE applications13.8.6
Interval for updating the J2EE application configuration file13.8.7
Reloading the Web applications13.8.8
Reloading the JSPs13.8.9
Relationship with the other functionality13.8.10
Reloading the J2EE applications using commands13.8.11
SettingsSettings for detecting updates and reloading J2EE applications13.8.12
NotesNotes and restrictions related to reloading13.8.13

Note: The functionality-specific explanation is not available for "Implementation" and "Operations".


Organization of this section
13.8.1 How to reload the J2EE applications
13.8.2 Scope of reloading
13.8.3 Class loader configuration used for reloading
13.8.4 Operations when an error occurs
13.8.5 Files for update detection
13.8.6 Update detection interval for J2EE applications
13.8.7 Interval for updating the J2EE application configuration file
13.8.8 Reloading the Web applications
13.8.9 Reloading the JSPs
13.8.10 Relationship with the other functionality
13.8.11 Reloading the J2EE applications using commands
13.8.12 Settings for detecting updates and reloading the J2EE applications
13.8.13 Notes and restrictions related to reloading