Erik Hatcher wrote:
Since we're moving forward with API refactoring discussions, on the topic of exceptions, perhaps its time to consider putting in our own exception class or hierarchy to decouple ourselves a bit from "IO". There are many in-memory non-disk-IO uses of these API's and having IOException being caught when it doesn't make sense (like iterating through tokens of a StringReader from an Analyzer, for instance).
Back-compatibility will be much simpler if new exceptions are subclasses of IOException. But adding a Lucene-specific exception hierarchy would be good hygiene. Does someone want to draft a proposal?
Doug --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
