使用Java异常的几条建议

The most important point to take away from this article is that exceptions are there for abnormal conditions and shouldn't be used to report conditions that can be reasonably expected as part of the everyday functioning of a method. Although the use of exceptions can help make your code easier to read by separating the "normal" code from the error handling code, their inappropriate use can make your code harder to read.

Here is a collection of the exception guidelines put forth by this article:

• If your method encounters an abnormal condition that it can't handle, it should throw an exception.
  
  
• Avoid using exceptions to indicate conditions that can reasonably be expected as part of the normal functioning of the method.
  
  
• If your method discovers that the client has breached its contractual obligations (for example, by passing in bad input data), throw an unchecked exception.
  
  
• If your method is unable to fulfill its contract, throw either a checked or unchecked exception.
  
  
• If you are throwing an exception for an abnormal condition that you feel client programmers should consciously decide how to handle, throw a checked exception.
  
  
• Define or choose an already existing exception class for each kind of abnormal condition that may cause your method to throw an exception.

 
http://www.javaworld.com/jw-07-1998/jw-07-techniques.html