> Kenneth,
>
> In a project I'm working on, we used the ServletContext to hold this
> information as you said. To get this information loaded at
> initialization time, we defined an initialization servlet and set it to
> be preloaded. After that, all global objects were ready and available
> for us to use.
>
> bab
>
> Brian Button [EMAIL PROTECTED]
> Senior Consultant Object Mentor, Inc.
> Products Review Editor C++ Report Magazine
Do you also save state when the ServletContext (ie, web application) dies
(servlet engine goes down, etc), using the initialization servlet?
--and--
> But ServletContext will not address your problem. The Singleton will.
>
> Regards,
>
> Subrahmanyam
Isn't the ServletContext a Singleton (on nondistributed systems)? From the 2.2
spec, section 4.1:
There is one instance of the ServletContext interface associated with each web
application deployed into a container.
-s
___________________________________________________________________________
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
