Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Date: Thu, 13 Jan 2005 19:38:28 +0100
Message-Id: <200501131838.j0DIcSgp032557@ajax.apache.org>
From: bugzilla@apache.org
To: tomcat-dev@jakarta.apache.org
Subject: DO NOT REPLY [Bug 33002]  -
    Containter does not return a 404 error for permanently unavailable Web
 components

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=33002>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=33002


------- Additional Comments From sastelting@earthlink.net  2005-01-13 19:38 -------
No, the specification states that the 404 error should be returned for permanent
unavailability in the service method. Exceptions in init are covered in
SRV2.3.2; the bug I refer to relates to the third paragraph of SRV2.3.3.2

For the init method, (SRV2.3.2.1) the specification implies that permanent
unavailability is treated the same way as a ServletException... the Web
component will be released, but the container can immediately attempt to
recreate the object.

I will provide a test case to you, but it will take me a day or two.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org