>From servlet-2_3-fcs-spec.pdf: SRV.9.9.1 Request Attributes ...If the location of the error handler is a servlet or a JSP page, the request attributes in Table SRV.9-1 must be set. javax.servlet.error.status_code java.lang.Integer javax.servlet.error.exception_type java.lang.Class javax.servlet.error.message java.lang.String javax.servlet.error.exception java.lang.Throwable javax.servlet.error.request_uri java.lang.String javax.servlet.error.servlet_name java.lang.String
Then it says that given a javax.servlet.error.exception, exception_type and message are redundant. Let it be. In the filter after request is processed by a servlet for 404 I get: status_code: null exception_type: null message: null exception: null request_uri: null servlet_name: action Is it a bug or do I miss something? Thank you. alex AL> Should javax.servlet.error.status_code attribute contain a AL> corresponding value in case of HTTP error? AL> Is it mandatory by the spec? AL> With Jetty that comes with current JBoss-3.2.0beta2 status_code is AL> null for 404 (haven't tried others). AL> But servlet_name has a value set in case of error. AL> The attributes were tested in a filter after request was processed by AL> a servlet. AL> Could someone, please, explain how it works and how it supposed to AL> work? AL> Thank you very much. AL> alex ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
