You could have your error handler check if the exception is a NestedServletException and its getRootCause() is a UnAuthorisedAccessException, and display the nested exception's error message in that case. You might want to use a separate <error-page> for NestedServletException. -- Len
On Fri, Jan 22, 2010 at 07:06, rotis23 <roti...@yahoo.com> wrote: > > Hi All, > > I use web.xml error-page handlers, some with error-code and other with > exception-type. At the end I have a catchall error-page that handles > java.lang.Throwable - users never see a stack trace and the world is a good > place. > > However, I've recently added a Hibernate security layer that throws a > UnAuthorisedAccessException that gets wrapped in a Spring > NestedServletException before it hits the error-page handlers. > > Now I understand that it tries to match the top level Exception in the stack > first then uses the next nested exception after that and so on until an > error-page is matched. The problem is that my catchall Throwable is matching > the NestedServletException first before the wrapped > UnAuthorisedAccessException hits its error-page handler. I need the users to > see that they don't have the privleges rather than a generic error messge - > I also need the catchall! > > Has anyone else dealt with this issue? I've been searchign for a couple days > on this now. > > TIA, rotis23 > -- > View this message in context: > http://old.nabble.com/error-page-problem---nested-exceptions-tp27272261p27272261.html > Sent from the Tomcat - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
