Why would you need to access the actual exception within your JSP view? I am not sure what your end goal is, but if you explain your idea further, I could give you a better answer.
I think it is bad style to have your JSP (or any view) know explicitly about Java exceptions - use your message key "error.data.page" as a state-flag to signal that a specific error was encountered to slightly change your GUI in response to the error or forward to an error-specific view, if you need to completely change the output based on an error. I think anything more complex should be left to either the Action to do additional processing before throwing an Exception or in a custom ExceptionHandler. Jason Rosen -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, September 17, 2002 9:53 AM To: [EMAIL PROTECTED] Subject: Struts Declarative Exceptions Questions I am making use of the Declarative Exceptions at the action level as such.. <exception key="error.data.page" path="/error/CustomerError.jsp" type="com.nlg.ar.common.exception.CustomerException"/> In this situation, is it possible to gain access to the actual thrown exception within the jsp page? I know this is not the best way to handle things but... Thanks -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
