Changes to server configuration

If you make any changes to the server or the server configuration while the server is running, for example, if you change the port number, you need to restart the server.

Changes to JSP, HTML, graphic and non-Java files

If you make any changes to a JSP file, HTML file, GIF file, JPG file, or similar resource, and save the file while the server is running, you will only need to refresh the Web Browser for the server to recognize the change. The state of the program is not lost.

Changes to servlets and related classes

If you make any changes to a servlet and save the file while the server is running, the servlet will be reloaded if you have enabled reloading for that application. If you have enabled hot method replace for the server, the changes will take place automatically without needing to refresh the browser. If you have disabled hot method replace, the server recognizes the change when you refresh the Web Browser and the state of the application is not lost. Session data for that project will be lost but the state of other projects within the application will be unchanged.

For WebSphere Application Server, the above rules also apply to any dependent classes or deployment descriptors of the Web project.

NOTE: If you modify the security or login configuration properties of the web.xml deployment descriptor running on WebSphere Application Server, you will need to restart the server.

Tip: To disable reloading, open your Web project with the deployment descriptor editor. On the Extensions page, clear the Reloading enabled check box.

Adding servlets, classes, or JSP files

If you add a new servlet, dependent class, or JSP file to a Web project while the server is running, the changes will be recognized if you have enabled reloading. If you have not enabled reloading, you will have to restart the EAR project if you are running WebSphere Application Server.

If you have enabled hot code replace in debug mode, changes to Java classes will be automatically recognized.

Changes to EJB resources

For WebSphere Application Server, the server will dynamically restart the EJB project in the EAR.

If you have enabled hot code replace in debug mode, changes to Java classes will be automatically recognized.

Changes to resources within an Enterprise Application project

For WebSphere Application Server, if you change any resource within an Enterprise Application project while it is running on the server, the server will dynamically restart the EAR.

For WebSphere Application Server v6.0, if you change any resources within the WebSphere Enhanced EAR editor, you need to restart the server and re-publish the application. The WebSphere Enhanced EAR editor is the Deployment page in the Application Deployment Descriptor editor.