[ http://jira.codehaus.org/browse/CONTINUUM-778?page=all ]
Carlos Sanchez closed CONTINUUM-778.
------------------------------------
Assignee: Carlos Sanchez (was: Napoleon Esmundo C. Ramirez)
Resolution: Fixed
Applied the patch with changes:
- no need to redirect to an action on error, in fact it can cause infinite loop
if the error is in webwork
- no need to separate two types of exceptions, at least for now
- use already existing error.jsp
- moved the exception logger interceptor to plexus-xwork integration as it can
be used elsewhere
- files without license header
> 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: Carlos Sanchez
> Fix For: 1.1
>
> Attachments: CONTINUUM-778-2.patch, 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
