Appendix B       Dynamic Reloading


Servlets, JSPs, and EJBs can be dynamically reloaded while the server is running. This allows you to change applications without restarting the server.

Whenever a reload is done, the sessions at that transit time become invalid. The client must restart the session.

---

Note

An EJB's interfaces and helper classes are not dynamically reloadable, so if you change them, you must restart the server. If an EJB changes during a session, the EJBContainer serializes the states of the EJB instances involved in the session and deserializes them after recreating the pool of instances.

---

---

Note

A resource such as a file that is accessed by a servlet, JSP, or EJB must be in a directory pointed to by the class loader's classpath. For example, the web class loader's classpath includes these directories: modulename/WEB-INF/classes modulename/WEB-INf/compiled_jsp modulename/WEB-INF/lib If a servlet accesses a resource, it must be in one of these directories or it will not be loaded properly.

---

Dynamic reloading is built into the server for servlets, JSPs, and EJBs. Changes made while the iPlanet Application Server is running are picked up the next time a request arrives for that servlet, JSP, or EJB.

Dynamic reloading for all classes (except unregistered JSPs, which are always reloaded) can be turned on or off using the registry entry SYSTEM_JAVA\Versioning\Disable (you can edit the registry using the kregedit tool). By default it is set to 1, indicating that dynamic reloading is disabled. A value of 0 enables dynamic reloading.