> -----Original Message-----
> From: Peter Brandt-Erichsen [SMTP:[EMAIL PROTECTED]]
> Sent: Thursday, December 21, 2000 1:46 AM
> To:   [EMAIL PROTECTED]
> Subject:      Re: creation of application wide objects
> 
> My apologies for the confusion and also for 
> misquoting David and you. 
> 
> So, it is possible to specify a set of servlets 
> to load on startup. That's awesome.
> 
> How do I point Tomcat to auto load servlets on
> start up, that are defined in my custom contexts?  
> Does Tomcat scan through each defined context's
> web.xml and just start loading all the servlets that are
> defined?
        [Kitching Simon]  
        That's exactly right. When tomcat starts a webapp, it
        checks the web.xml file for that webapp, and starts
        any servlets specified as load-on-startup.

> Also, if I had three sevlets to auto load would I specify
> 
> <load-on-startup>
> 3
> </load-on-startup>
        [Kitching Simon]  
        No, the number indicates the *order* of startup. Servlets
        with lower load-on-startup numbers are *guarunteed* to
        get started before servlets with higher numbers. If several
        servlets are define with the same number, then they get 
        started in any order. See the sun specs for the precise 
        definition of this behaviour.

> Peter 
> 
> 
> -----Original Message-----
> From: craig mcclanahan <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Wednesday, December 20, 2000 4:31 PM
> Subject: Re: creation of application wide objects
> 
> 
> >Intergate wrote:
> >> 
> >> Alex,
> >> 
> >> Were you successful with this auto loading solution?
> >> It is something that I have been searching for...
> >> 
> >> I seem to remember a message a while back from someone
> >> on the list that indicated that the
> >> 
> >> >>          <load-on-startup>
> >> >>               1
> >> >>           </load-on-startup>
> >> 
> >> wasn't implemented as of Tomcat 3.2.1 and would not
> >> be available until 4.0.
> >> 
> >
> >That is not correct -- this capability works in Tomcat 3.2.1.  The
> >confusion is probably due to the issue pointed out in my next response.
> >
> >> Also, David wrote this morning that Tomcat 3.2.1 does
> >> not read the web.xml file and that it shouldn't even be
> >> included in the distribution anymore??
> >
> >Tomcat 3.2.1 does not read the web.xml file in $TOMCAT_HOME/conf.  It
> >*definitely* reads the web.xml file in your application's WEB-INF
> >directory -- that is where you should be doing your customizations.
> >
> >> 
> >> P.
> >
> >Craig McClanahan
> >
> 

Reply via email to