On 10-06-2010 23:38, Mike Schilling wrote:
"ClassCastException" <zjkg3d9gj56@gmail.invalid> wrote in message
Does the servlet<->container API/protocol/whatever not include an
explicit way for a servlet to signal a fatal error to the container? Let
alone to perform just-once initialization, prior to handling requests,
which can fail?
Yeah, that you can do. There's an init() method, and if it throws an
exception the servlet is never enabled (at least, in containers I know
of. Not sure if that's part of the spec.)
The servlet specs say:
<quote>
During initialization, the servlet instance can throw an
UnavailableException or a
ServletException. In this case, the servlet must not be placed into active
service
and must be released by the servlet container. The destroy method is not
called as it
is considered unsuccessful initialization.
</quote>
so if the exception thrown is a ServletException, then there
are no servlet available.
Cool. I'd be surprised if, say, Tomcat enabled servlets for a web app whose
init() method threw a RuntimeException either.