Could one exception be a subclass of another? Some of the methods throw both, and that seems to be a loss of abstraction (not to mention a bit wordy)