[ http://jira.codehaus.org/browse/CONTINUUM-778?page=all ]
Napoleon Esmundo C. Ramirez updated CONTINUUM-778:
--------------------------------------------------
Attachment: CONTINUUM-778-2.patch
CONTINUUM-778-2.patch provides the support for chained exception handling.
Chaining the exceptions to actions will enable the checking of levels of
details to show to the resulting page. The ExceptionLoggingInterceptor would
have to deal with server logs in the meantime.
> 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-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
