Exception handling - Improve the exception reporting with more context information ---------------------------------------------------------------------------------- Key: JBSEAM-2601 URL: http://jira.jboss.com/jira/browse/JBSEAM-2601 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Shane Bryzak Fix For: 2.1.0.GA Once we clean up #{exception} and #{handledException} (remove one...), we need to add more context information. I don't know how to do that so I don't have any recommendation how this could be implemented - only that I heard that Tapestry has good exceptions. What I need (especially now in production) is more information about the request that triggered the exception. For example, I want to be able to reproduce the exception by executing the same GET/POST request. So this needs to include request header/parameter information and information about the server-side state (is it a new session, etc). I need to be able to access that information in my exception handler and for production optionally have it logged. Without this, I need to rely on user error reports which so far have not resulted in a single bugfix of the wiki, because I can't reproduce what the users are doing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira