error handlers #115
Description
The intention of the vernacular is that non-internal exeptions, both external
errors and programming errors, plus all other unexpected
throwables, are logged and reported to the intended audience resp.
administrators and developers), before the leave the "execution
environment", which should also be gracefully shut down when such errors occur.
We envisage different ways of handling this for CLI applications, GUI
applications of different types (there probably is a different way of
handling things for eclipse RCP and Swing applications), web applications (war)
and enterprise applications (session beans).
Both the logging and communication will probably be done using a logging
framework, probably commons logging to be independent
of a specific logging framework. If I am not mistaken, both log4j and Java
logging can also send email (to administrators and
developers).
The code to handle this is intended to be part of this library, and will be
added as the need occurs (or submissions are received :-)).
Notably, in the old ppw-jsp or ppw-servlet, there are error handling pages that
probably can and should be reenabled here.
Original issue reported on code.google.com by jandockx on 29 Jul 2008 at 8:21