[ http://jira.codehaus.org/browse/CONTINUUM-778?page=comments#action_72184 ] Jesse McConnell commented on CONTINUUM-778: -------------------------------------------
I recently added a new baseclass in place of the PlexusActionSupport class on the trunk that does the initialization check that used to be on 1.0.3 where every page had a check to see if the continuum instance was initialized, and if it wasn't to redirect to the configuration edit screens... perhaps instead of chaining the exception itself from whatever action throws it, we could just add a method to that ContinuumActionSupport baseclass that logs the exception to the logger and then throw the exception normally for the exception interceptor to do its business... just a thought > show internal error page on unhandled exceptions > ------------------------------------------------ > > Key: CONTINUUM-778 > URL: http://jira.codehaus.org/browse/CONTINUUM-778 > Project: Continuum > Issue Type: Sub-task > Components: Web interface > Affects Versions: 1.0.3 > Reporter: Carlos Sanchez > Assigned To: Napoleon Esmundo C. Ramirez > Fix For: 1.1 > > Attachments: CONTINUUM-778.patch, error-mapping.patch > > > It's possible to setup a servlet filter or something similar that maybe > webwork already has (Struts has it) to catch all unhandled exceptions, log > them to the log file and redirect the user to a "internal error" page. > Related to this we should make ContinuumException a RuntimeException, don't > catch it in the web layer and let the previous mechanism do it. We'll save a > lot of exception handling code not needed. > Note that this is only for system exceptions, eg. if database is down, and > not model exceptions, eg. when looking up by id it the record doesn't exist. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
