Hi, >Is there a way to programmatically make the Context unavailable?
Actually, I'd like to add to my previous message. There *is* at least one portable way to do this. If you initialize your singleton from a ServletContexteListener#contextInitialized method and throw an exception there, the container will mark the whole webapp as unavailable automatically. However, the filter approach I suggested may still be superior as it's more dynamic: i.e. if the DB drops while your app is running, the filter approach will still work while the above listener approach will not. Yoav Shapira http://www.yoavshapira.com This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
