Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[stellation-res] Error Handling In Stellation

Hi Jonathan,

In discussing error handling, you might find the following paper (documenting a Pattern Language for Error Handling) to be interesting and useful.

<http://www.objectarchitects.de/arcus/cookbook/exhandling/index.htm>

--
Onorio Catenacci


At 01:55 PM 1/11/03 -0500, you wrote:
Some time ago Mark floated a suggestion about using AspectJ. I would like to
start making use of it, and in particular I would like to use it to ensure
that we have consistent handling for all exceptions that we throw.

As I see it, we have the following major classes of exceptions.

1. Programming errors
These derive from "impossible" paths that became possible or from warranted
paranoid checking that turns out to be needed. For these exceptions, I would
like to ensure that we do the following:

   a) Log the exception.
   b) Produce a stack trace

2. User errors
These derive directly or indirectly from bad user input. I would like to
ensure that we do the following:
   a) Log the exception
   b) For command line programs, tell the user what is wrong. It may be
possihble to handle user error reporting for GUI programs as well, but it
will take some careful analysis to determine if this can be clearly enough
codified.

3. Data corruption errors
Again make sure that we do the following:

   a) Log the exception.
   b) Produce a stack trace

4. Non-local transfer of control
These exceptions need no special handling when they are thrown.



Back to the top