Hi,
<snip>
>So, again, replacing a single action object (and it's associated data) is
>quick and painless. But what if you are making broad changes that affect a
>workflow, for example, which affects many classes and default target
>pages?? One possibility might be to ignore this and allow your error
>handling to kick in when users make requests for actions/pages that are no
>longer supported. It seems to me that creating a whole new
>Hashtable object
>and replacing it in the servlet context
>with servlet.getServletContext().setAttribute("urilist", uriList);
>
>would not solve this problem; since users currently actively involved in a
>specific workflow might be "orphaned." I guess, if you need to modify the
>app that radically, then some sort of controlled shutdown/startup might be
>better....
Agreed. I believe unless its an emergency, since most sites usually dont
have activity during the wee hours of the night, its best to shut down and
restart the server during off-peak hours..or for those sites that do get
hits 24/7, log activity for a week and see when the least traffic is on. A
controlled shutdown/restart should be relatively quick, except in restoring
connections to the database for the connection pool.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
Some relevant FAQs on JSP/Servlets can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
http://www.jguru.com/jguru/faq/faqpage.jsp?name=JSP
http://www.jguru.com/jguru/faq/faqpage.jsp?name=Servlets
