Hi there, I played a little bit with the new servlet runner (shipped with the new JSDK2.1) and noticed the following behaviour: When a servlet throws an UnavailableException during init(), the servlet engine should regard the servlet as not fully initalized and should try to reload the servlet some time later (if the servlet has been flagged as only temporarily not available), if I understand the specs properly. Now the servlet runner seems to ignore these exceptions: After init() has been interrupted by the exception, following requests reach service() - but the servlet maybe in an inconsistent state! The servlet should not proceed to the "ready" state in the lifecycle scheme IMHO. bye Chris ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
