> In a servlet 2.2 world, what most people do is declare a servlet to be
> <load-on-startup> and initialize things in the init() method of that
> servlet.  This is relying on the container to never unload that servlet
> for the lifetime of the app (Tomcat doesn't unload anything until shutdown
> time), but it basically works.
>
> Craig McClanahan

Good point. If the Servlet were to be unloaded, another instance would need to be
loaded right away. Is there any (platform-independent) way to guarantee that at
least one instance of a Servlet will always be loaded, even if it's not set up to
handle HTTP requests?

-Erik

Reply via email to