Peace all (James, Michael, and David :o)
Just a note, regarding James' problem with singletons and
reloadable servlets -- from the Servlet 2.2 specs (if I may quote
the entire section?) --
(section 4.6) Reloading Considerations:
"Many servlet containers support servlet reloading for ease of
development. Reloading of servlet classes has been accomplished
by previous generations of servlet containers by creating a new
class loader to load the servlet which is distinct from class
loaders used to load other servlets or the classes that they
use in the servlet context. This can have the undesirable side
effect of causing object references within a servlet context to
point at a different class or object than expected which can
cause unexpected behavior. Therefore, when a Container Provider
implements a class reloading scheme for ease of development,
they must ensure that all servlets, and classes that they may
use, are loaded in the scope of a single class loader
guaranteeing that the application will behave as expected by
the Developer."
Isn't iPlanet sold by Sun now?
What do you make of it, James?
Section 4.3.1 before this, sais mustn't use the servlet context
for _distributed shared store_ -- do it with sessions, EJB,
or as David suggested, instead.
HTH
-- Ia
--
Ia ([EMAIL PROTECTED])
The Real World Is A Special Case
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
