NB: Sorry if this a double posting but for some reason it didn't get through
the first time.
On 3/1/2011 7:52 PM, Caldarale, Charles R wrote:
> In the 3.0 spec, it's in section 11.6 (was 10.6 in the 2.5 version). The key
statements are:
Yes, that's what I was referring to.
> Because of the s
> From: Olivier Lefevre [mailto:lefev...@yahoo.com]
> Subject: Re: Vetoing the start of a webapp
> Sorry, can you give me the actual section: are you
> referring to §11.6?
In the 3.0 spec, it's in section 11.6 (was 10.6 in the 2.5 version). The key
statements are:
"The
It's in the servlet spec.
Sorry, can you give me the actual section: are you
referring to §11.6?
-- O.L.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.
> From: Olivier Lefevre [mailto:lefev...@yahoo.com]
> Subject: Re: Vetoing the start of a webapp
> is this Tomcat-specific or is it spelled out in the
> servlet spec somewhere?
It's in the servlet spec.
> Yes but that does not make ServletContext a stand-in
> for weba
On 3/1/2011 3:14 PM, Caldarale, Charles R wrote:
Normally, you would put such conditional activation code in a
ServletContextListener, and have it throw an exception if things
> are not to your liking. Doing so would prevent any further use
> of the webapp.
OK but I have the same question as to
> From: Olivier Lefevre [mailto:lefev...@yahoo.com]
> Subject: Vetoing the start of a webapp
> But what if the webapp has several servlets and you
> want to abort (or undo) the loading of the whole
> collection if any of the members fail to load: is
> there already an accepted best practice for t
