My last group question regarded class paths and multiple domains --
thanks for the
various suggestions on this, and I did in fact find out a lot about this issue
(which basically amounted to "Tomcat is brain-dead with respect to
multiple domains
from one Tomcat/Apache process", though I managed to come up with
some complicated
not-entirely-satisfying solutions.)
This next question is perhaps more simple and like the last one is certainly
generally applicable:
What's the "simplest" way to have "persistent beans" inside JSP pages?
In other words, I have a bean that's scoped "session", for example. What's
the simplest way to make that bean "persist" over multiple sessions?
"Simplest" implies "lowest cost" and also "least amount of fiddling"...
Thanks again! You can see some of my recent work on this subject in my .sig
even though the .jsp pages are currently being replaced by servlets...
/t
....formal model of chess <http://editev.com/servlet/chess>.............
...a random game of chess <http://editev.com/servlet/chess?refresh=0>...
............documentation <http://editev.com/chess>.....................
===========================================================================
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
