André Warnier wrote: > Hi. > > About the <load-on-startup> item in web.xml, the Servlet Spec 2.5 has > this to say (p 128) : [...] > My questions are : > > 1) In the case of Tomcat 5.5 and higher, is there a way to *prevent* a > deployed application to be loaded and/or started at Tomcat startup ? > (basically only be started when the first call to it is made)
I don't think so. However, if you don't have load-on-startup at all, the servlets will only be loaded when first referenced. As to when the JSP compilation happens, I'm not certain (but once compiled, I think also the servlets that are generated from JSPs are only loaded when first referenced). It seems that you're somewhat mixing loading of a single servlet with loading of the whole webapp. > 2) what is the interpretation of a missing <load-on-startup> tag ? Looks like I answered this question in the above. > A related question : > > Using the Tomcat Manager app, I can "stop" and "start" an application. > What really happens there, internally ? What does it mean that an > application is stopped ? Does it mean that from now on Tomcat somehow > "catches" the calls to these URLs, and diverts them to some internal > webapp that responds : no such application, or ? A webapp has quite a bit of context, in addition to the servlets, JSPs and static resources. This context is what is being built on startup (and torn down when stopping the application). This context is described in the per-application web.xml; context init parameters, context listeners, declared servlet mappings, ... . -- ..Juha --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
