Wow... that's kinda interesting.  I'll have to test out the behaviour in
Tomcat.  Thanks for the info. =)

On Wed, 2003-02-12 at 15:43, [EMAIL PROTECTED] wrote:
> Reply in Line
> 
> 
> 
> 
> Richard Wallace <[EMAIL PROTECTED]> on 13/02/2003 02:19:41
> 
> Please respond to "Avalon framework users" <[EMAIL PROTECTED]>
> 
> To:    Avalon framework users <[EMAIL PROTECTED]>
> cc:
> 
> Subject:    Re: [Newbie] Running Merlin
> 
> On Wed, 2003-02-12 at 06:40, Stephen McConnell wrote:
> > On the subject of early failure - I don't see how your going to get a
> > fail condition earlier than init() - unless Merlin is hosting the
> > web-server --> webserver is hosting a web-app --> web-app is suppled
> > with services based on dependencies that are pre-assembled by Merlin
> > (which is possible using the embedded Tomcat approach).
> >
> 
> Actually, if you specify the servlet to be loaded at startup the init is
> called right away.  Check out the <load-on-startup> element for a
> servlet.
> 
> The short and skinny of it is that if the value is 1 or more then the
> servlet is initialized when it is deployed.  The value determines where
> it is in the order of initialization, with 1 being the highest
> precedence.  So, to have a servlet be the first loaded when deployed you
> want your web.xml to look like the following.
> 
> <web-app>
>              ...
>              <servlet>
>                          ...
>                          <load-on-startup>1</load-on-startup>
>              </servlet>
> 
>              ...
> </web-app>
> 
> Using this parameter the initialization will fail at deployment giving
> you the error messages before the first user hits it.
> 
> <REPLY>
> I actually found that on WebSphere 4.0 <load-on-startup> with any value
> will
> load the servlet on startup. We had previously believed that '0' would not
> load the servlet. This caused us some problems. Meant I had to get changes.
> 
> Not sure what other Web Containers do orwhether this behaviour is
> non-standard.
> 
> You may need to make sure about this behaviour.
> </REPLY>
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ****************************************************************
> NOTICE - This message is intended only for the use of the 
> addressee named above and may contain privileged and 
> confidential information.  If you are not the intended recipient
> of this message you are hereby notified that you must not 
> disseminate, copy or take any action based upon it.  If you 
> received this message in error please notify HIC immediately.
> Any views expressed in this message are those of the individual
> sender, except where the sender specifically states them to be
> the views of HIC.
> ****************************************************************
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-- 
Richard Wallace
AIM, Inc. (www.a--i--m.com)
Information Systems Consultants

"Providing New Technology,
     the Old-Fashioned Way"


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to