WAR files

 

+

Search Tips   |   Advanced Search

 

Overview

There are several changes that one can make to WAR files cycling application servers.

 

Change an existing JSP file

Place the changed JSP file directly in...

application_root/module_name

...or the appropriate subdirectory. The change will be automatically detected and the JSP will be recompiled and reloaded.

Hot deployment	Not applicable
Dynamic reloading	Yes

 

Adding a new JSP file to an existing application

Place the new JSP file directly in...

application_root/module_name

...or the appropriate subdirectory. The new file will be automatically detected and compiled on the first request to the page.

Hot deployment	Yes
Dynamic reloading	Yes

 

Change an existing servlet class (editing and recompiling)

1. Place the new version of the servlet .class file directly in the...

   application_root/module_name/WEB-INF/classes

   If the .class file is part of a Jar file, one can place the new version of the Jar file directly in...

   application_root/module_name/WEB-INF/lib

   In either case, the change will be detected, the Web application will be shut down and reinitialized, picking up the new class.

2. If automatic reloading is not enabled, restart the application.

Hot deployment	Not applicable
Dynamic reloading	Yes

 

Change a dependent class of an existing servlet class

1. Place the new version of the dependent .class file directly in...

   application_root/module_name/WEB-INF/classes

   If the .class file is part of a Jar file, one can place the new version of the Jar file directly in...

   application_root/module_name/WEB-INF/lib

   In either case, the change will be detected, the Web application will be shut down and reinitialized, picking up the new class.

2. If automatic reloading is not enabled, restart the application.

Hot deployment	Not applicable
Dynamic reloading	Yes

 

Add a new servlet using the Invoker facility or adding a dependent class to an existing application

1. Place the new .class file directly in...

   application_root/module_name/WEB-INF/classes

   If the .class file is part of a Jar file, one can place the new version of the Jar file directly in...

   application_root/module_name/WEB-INF/lib

   In either case, the change will be detected, the Web application will be shut down and reinitialized, picking up the new class.

   This case is treated the same as changing an existing class. The difference is that adding the servlet or class does not immediately cause the Web application to reload because the class has never been loaded before. The class simply becomes available for execution.

2. If automatic reloading is not enabled, restart the application.

Hot deployment	Yes
Dynamic reloading	Not applicable

 

Add a new servlet, including a new definition of the servlet in web.xml

1. Place the new .class file directly in the...

   application_root/module_name/WEB-INF/classes directory

   If the ".class" file is part of a Jar file, one can place the new version of the Jar file directly in...

   application_root/module_name/WEB-INF/lib

   You can edit the web.xml file in place or copy it into the...

   application_root/module_name/WEB-INF/classes directory

   The new .class file will not trigger a reloading of the application.

2. Restart the application.

Hot deployment	Yes
Dynamic reloading	Not applicable

 

Change the web.xml file of a WAR file

1. Edit the web.xml file in place or copy it into the metadata_root/module_name/WEB-INF directory.

2. Restart the application.

Hot deployment	Yes
Dynamic reloading	Yes

 

Change the ibm-web-ext.xmi file of a WAR file

Edit the extension settings as needed. We can change all of the extension settings. The only warning is if you set the reloadInterval property to zero (0) or the reloadEnabled property to false, the application no longer automatically detects changes to class files. Both of these changes disable the automatic reloading function. The only way to re-enable automatic reloading is to change the appropriate property and restart the application.

Hot deployment	Not applicable
Dynamic reloading	Yes

 

Change the ibm-web-bnd.xmi file of a WAR file

1. Edit the bindings as needed. We can change all of the values but ensure that the entities you are binding to are present in the configuration of the server.

2. Restart the application.

Hot deployment	Not applicable
Dynamic reloading	Yes

---

 

Related Tasks

Hot deployment and dynamic reloading

 

---