Have considered this a bit further, seems the first step would be to mark the Servlet as unavailable by ensuring init throws an UnavailableException. But then what? As far as I can see there is no way to check if a Servlet is unavailable using Tomcat's built in MBeans. Is this true?
Derek Alexander wrote: > > Deploying an app with a runtime dependency missing resulted in > Servlet.init() throwing a ServletException caused by a > ClassNotFoundException. > > Tomcat manager however reported the application as running. I guess it was > to a certain extent, however it would have been more useful to me to know > that there was a general problem with the app. > > Anyone know a good generic way to check that an app has at least managed > to initialise ok. > > Cheers > -- View this message in context: http://www.nabble.com/generic-way-of-checking-application-status--tf4850640.html#a13948641 Sent from the Tomcat - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
