Inconsistent Error and Exception Handling

From OpenPetra Wiki
Revision as of 11:03, 3 May 2011 by Christiankatict (talk | contribs) (Moved input from WolfgangU to new page 'A Use Case for a Custom Exception'.)
Jump to navigation Jump to search

Overview

We do not yet have a consistent way of handling errors in all situations. This is strongly desired.

TODO: Extend the Error and Exception Handling Policy - especially in the areas of Client and Server error handling.


Input from ThiasG

Expected System-Exceptions shall be caught and be put into an OpenPetra-specific Exception. This help to differentiate between programmed errors and expected Exception conditions.


Until now, we have not added anything about handling the exception, e.g. handling the exception in the client, aborting the current function, logging the exception and showing the error to the user.


We need to add something about handling extreme cases, such as

  • Losing connection to DB;
  • Client-Server/Server-Client connection;
  • other cases?

What to do in such situations: Do we stop the client session? In which cases the server needs to stop? - Not all error conditions are initiated by a function call from the client.

--Thiasg 09:27, 31 January 2011 (UTC)

Retrieved from ‘https://wiki.openpetra.org/index.php?title=Inconsistent_Error_and_Exception_Handling&oldid=2112’