What are you doing with regard to production JSP/Servlet engines and installing new class files? I am using Apache 1.9/Tomcat 3.1 and from reading the posts and from our experiencce, it seems like I must stop and start Apache and Tomcat to install the new version of a class file. So in a production environment, the current "state" of sessions will be lost when this happens. How do you deal with this? Are there servlet engines that handle class updates better? Thanks
Resin sounds promising, how does it handle this scenario. I have a standard header bean and it takes 3 parameters to generate each page's header. Now on the development box I change this bean to require 4 parameters and I update the JSP pages that use this bean so that they feed it the required parameters. With Tomcat to deploy these changes I need to copy over the .jsp and .class files and then stop and start Apache/Tomcat, and people already logged in loose their session. Can Resin handle this scenario without restarting? Another scenario is that someone is logged into our site and they have items in their shopping cart, which is a java class. On my test box I modify the cart class. Now I need to deploy it. Again with Apache/Tomcat I must stop and start the server processes which empties the JVM and therefore the customer's cart. How does Resin handle this and resolve any differences between the old and new revisions of the cart class?
Originally posted by Frank Carver: I use Resin, from http://www.caucho.com/ which reloads classes and wars if they change without needing a reboot and usually without affecting other web-apps.