> 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
- Such a thing as server startup class? Erik Weber
- Re: Such a thing as server startup class? Pier P. Fumagalli
- Re: Such a thing as server startup class? Erik Weber
- RE: Such a thing as server startup class? Filip Hanik
- Re: Such a thing as server startup cl... Pier P. Fumagalli
- Re: Such a thing as server start... Erik Weber
- Re: Such a thing as server start... Pier P. Fumagalli
- Re: Such a thing as server start... Craig R. McClanahan
- Re: Such a thing as server startup class? Pier P. Fumagalli
- Re: Such a thing as server startup class? Craig R. McClanahan
- Re: Such a thing as server startup class? Erik Weber
- Re: Such a thing as server startup class? Craig R. McClanahan
- Re: Such a thing as server startup cl... Erik Weber
- Re: Such a thing as server start... Pier P. Fumagalli
- Re: Such a thing as server start... Erik Weber
- RE: Such a thing as server startup cl... Greg Trasuk
- Re: Such a thing as server start... Pier P. Fumagalli
- Re: tomcat on mac os 10 with virtual PC Adam Wildavsky
- Re: tomcat on mac os 10 with virtual PC Pier P. Fumagalli
- Re: tomcat on mac os 10 with virtual PC Adam Wildavsky
- Re: tomcat on mac os 10 with virtual PC Pier P. Fumagalli
