Error reporting

[mikedougherty]

I'm having a bit of trouble figuring out how error reporting is suppose to work. I have an exceptions.xml file to catch exceptions.

 <exception class="java.lang.RuntimeException">
 <redirect view-id="/fatalError.xhtml">
 <message>Unexpected error, please try again</message>
 <endConversation />
 </redirect>
 </exception>
 <exception>
 <redirect view-id="/fatalError.xhtml">
 <message>Unexpected error, please try again</message>
 <endConversation />
 </redirect>
 </exception>

Which seems to work if the Exception is thrown early enough in the page rendering process. However, it does not always seem to catch the exceptions. The best I can figure is that it doesn't work when the page is rendered partially, and then an Exception is encountered. The makes sense because once an HttpServletResponse has been committed you can't then decide to redirect.

I need to find a way to configure Seam (or maybe it's JSF) when it reports Errors and/or Exceptions. The default, which includes StackTrace, Component Tree, Scoped Variables, etc, is fine while in development. But once the application goes to production (or test) I need to be able to eliminate all that and just print a nice message.

Where, how can I configure the reporting of exceptions in my application?

[pmuir]

http://wiki.jboss.org/wiki/Wiki.jsp?page=SeamProblemsFAQ

I've just added an entry at the bottom to answer this hopefully. Nice analysis!

[mikedougherty]

Thanks for posting that, but it might have helped if I wasn't such a dweeb! I had totally forgot about:

 <context-param>
 <param-name>facelets.DEVELOPMENT</param-name>
 <param-value>false</param-value>
 </context-param>

I knew there was a "debug" flag there someplace I needed to change, but I was thinking it was the <core:init debug="false" />. Doh!