that's what I was afraid of. So, in response to Dave's original question:
unless you make sure you only load that one servlet at startup, this is not
the way to ensure that a specific servlet is initialized first.
Rob
-----Original Message-----
From: Nic Ferrier [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 26, 2000 3:20 PM
To: [EMAIL PROTECTED]
Subject: Re: Servlet Spec and Global Startup Servlets
>>> Rob van Oostrum <[EMAIL PROTECTED]> 26-Jun-00 2:09:18 PM >>>
>yes, but does this guarantee you the order in which
>the different <load-on-startup> servlets are loaded
>on startup?
No. It doesn't.
Different servlet containers *may* implement different loading
schemes... it would probably depend on the parser. I imagine most
would load in the order given in the file.
But from what I rememeber this is NOT a gaurantee.
Searching back through the archives might help with this because it
was discussed before.
Nic
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
