>>>>>>
As an alternative to singleton classes, you might also consider
storing these
objects in the ServletContext via the setAttribute() method. Such
objects are
always available to your servlet via:
getServletContext().getAttribute("KEY");
and, as an extra benefit, you can run more than one application on
the same
server if you need to (each in its own ServletContext), without
running into
name clashes on your Singleton classes.
<<<<<
Craig,
When you say "you can run more than one application on the same
server if you need to (each in its own ServletContext),", I assume
you mean
that you can run the applications in different PROCESSES on the same
MACHINE.
If not, how do you get more than one ServletContext in the same JVM?
--Olu E.
___________________________________________________________________________
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
