Just implement them as normal java singleton objects and get them to load
up when the Server is started up.
Vinod
Pigeon
<[EMAIL PROTECTED]> To: [EMAIL PROTECTED]
Sent by: "A mailing cc:
list for discussion Subject: Servlet environment...
about Sun
Microsystem's Java
Servlet API
Technology."
<SERVLET-INTEREST@JAV
A.SUN.COM>
05/05/00 12:55 PM
Please respond to "A
mailing list for
discussion about Sun
Microsystem's Java
Servlet API
Technology."
Dear all,
I'm new to servlets and I'd like to ask some questions about the
servlet
environment.
As described in the servlet life cycle, the server loads and initilizes
a servlet, and then the servlet will handle requests and at the end the
server will remove/destroy the servlet.
So I'm wondering how I should implement a system which has some
persistant, singleton objects, or some objects which exist and run all the
time as long as the java environment is being launched. (For example, some
sorts of pool which keep a list of objects, so that servlets and other
object within the environment can use them.)
Thanks a lot.
Pigeon.
___________________________________________________________________________
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
___________________________________________________________________________
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
