Article:		Three Rules for Effective Exception Handling
Subject:		Don't forget good messages and thinking about how to handle loops.
Date:		2003-12-08 20:10:52
From:		emeade
Exception messages targeted for users not developers. Assume that some end user will be up at 2:00AM trying to meet some deadline when this exception is encountered.  Give her a chance and include filenames, URIs<a/>, classnames, or whatever you have that could help. Personally  I think Jakarta's Ant does a great job of giving helpful error messages. Looping through objects and calling methods that can throw exceptions can also be a challenge.  Should one failure cause everything to stop?