On 2/28/2011 6:09 PM, Caldarale, Charles R wrote:
The servlet, or the webapp?
The webapp in this case: the servlet that might fail is the "worker" servlet, the others more in a supporting role (e.g., UI). So if it fails the whole webapp should shut down.
Why don't you simply throw a ServletException in the init()
> method of the servlets of interest? OK. But how to communicate to the other servlets of the webapp that they, too, should commit suicide? Are they guaranteed to be created in a certain order? In that case I'd put the worker servlet ahead and then maybe there is a way to leave a breadcrumb behind after its death as a sign to the others that they should not proceed. -- O.L. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
