This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
My understanding is that we need to restart server (Websphere v5.0 Test Environment) only if we make any changes to Server Configuration. No need to restart server for any changes in JSPs, Servlets etc. Please let me know if I'm wrong.
....you have to restart if you changed your EJB that requires a regeneration of rmi stubs....
SCJP 1.4<br />SCWCD 1.4
Joined: Oct 16, 2000
Thanks for the response. I got more information about restarting the server from IBM site. I'm little bit confused. According this article we need to restart the server only if we make changes to server configuration.
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 Web resources 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. The server recognizes the change when you refresh the Web Browser and the state of the application is not lost. If you have not enabled reloading for the running application, you must manually restart the individual project within your application if you are running WebSphere Application Server V4. Session data for that project will be lost but the state of other projects within the application will be unchanged. You can restart the project from the project's pop-up menu in the Navigator view. For WebSphere Application Server V5, if you do not have reloading enabled, you must restart the EAR. If you are running Tomcat and do not have reloading enabled, you will need to restart the server. For WebSphere Application Server, the above rules also apply to any dependent classes or deployment descriptors of the Web project. 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. For Tomcat, a restart of the server is required for any of these changes. 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, or restart the server if you are running Tomcat.
Changes to EJB resources For WebSphere Application Server V4, you must restart the EJB project if you make any changes to EJB implementations, dependent classes, deployment descriptors, or if you add either any new enterprise beans or dependent classes to the module. If you modify an EJB interface or the interface's dependent classes, you must first publish the project, and then restart it. Automatic reloading of individual classes is not supported. For WebSphere Application Server V5, the server will dynamically restart the EJB project in the EAR. Important: Tomcat does not support EJB testing and publishing.
Changes to resources within an Enterprise Application project For WebSphere Application Server V4, if you change any resource within an Enterprise Application project while it is running on the server, you must restart the affected project. For WebSphere Application Server V5, if you change any resource within an Enterprise Application project while it is running on the server, the server will dynamically restart the EAR. Tomcat does not support Enterprise Application project testing and publishing.