Changing or adding WAR files
You can change web application archives (WAR files) on application servers without having to stop the server and start it again.
About this task
However, a Java EE 5 or later module can exist within an application that includes pre-Java EE 5 files and uses the .xmi file name extension.
The ibm-webservices-ext.xmi, ibm-webservices-bnd.xmi, ibm-webservicesclient-bnd.xmi, ibm-webservicesclient-ext.xmi, and ibm-portlet-ext.xmi files continue to use the .xmi file extensions.
There are several changes that you can make to WAR files without stopping the server and starting it again.
The following table lists the changes that you can make by manipulating a WAR file on the server where the application is deployed. The table also states whether you use hot deployment or dynamic reloading to make the changes.
Change | Hot deployment | Dynamic reloading |
---|---|---|
Change an existing JavaServer Pages (JSP) file. | Not applicable | Yes |
Add a new JSP file to an existing application. | Yes | Yes |
Change an existing servlet class by editing and recompiling. | Not applicable | Yes |
Change a dependent class of an existing servlet class. | Not applicable | Yes |
Add a new servlet using the Invoker (Serve Servlets by class name) facility or add a dependent class to an existing application. | Yes | Not applicable |
Add a new servlet, including a new definition of the servlet in the web.xml deployment descriptor for the application. | Yes | Not applicable |
Change the web.xml file of a WAR file. | Yes | Yes |
Change the ibm-web-ext.xmi file of a WAR file. | Not applicable | Yes |
Change the ibm-web-bnd.xmi file of a WAR file. | Not applicable | Yes |