Tim Lucia wrote:
> You can't, and generally don't want to stop Tomcat (the server) when an
> application is mis-configured. Instead, you can stop (mark unavailable)
> your application. One way to do this is to throw an exception inside a
> ServletContextListener, if it detects wrong values inside
You can't, and generally don't want to stop Tomcat (the server) when an
application is mis-configured. Instead, you can stop (mark unavailable)
your application. One way to do this is to throw an exception inside a
ServletContextListener, if it detects wrong values inside the configuration
file: