ErrorHandlingStory

Description

In order to give some usefull feedback to the enduser when something goes wrong ( very unlikely offcourse ) the exception hiearchy and handling has to be extended to allow for more descriptive error messages.

Resources

• Article on EJB exception handling
• Disscussion about the above article and where to log errors

Functional specifications

• Inventarise usefull error messages. For example the synchronisation class should distinguish connection errors and synchronisation errors.
• Create exception hierarchy
• Implement the error pages

Budget/Hours

task	estimate	todo	spent	developer
Inventarise usefull error messages	2	0	2	Ivo
Create exception hierarchy (and implement them)	6	0	4	Ivo
Implement the error pages	4	0	4	Ivo
Total	12	0	10

Notes

Usefull exception subclasses:

• DaoException?
  • InvalidURIDaoException?
  • ConnectionDaoExeption?
  • SSLDaoException?
  • IcalParserDaoException?

Discussion

Is the preferred way to handle the exceptions to throw a specialized DaoException subclass that will be wrapped in a WebicalException and then check the cause of the WebicalException? in the web layer? Or should every DaoException subclass be matched with a WebicalException subclass to ease the exception handling?

-- IvoVanDongen - 23 Oct 2006