lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benson Margulies (JIRA)" <j...@apache.org>
Subject [jira] Created: (LUCENE-1264) Use of IOException in analysis component method signatures leads to poor error management
Date Wed, 16 Apr 2008 23:55:21 GMT
Use of IOException in analysis component method signatures leads to poor error management
-----------------------------------------------------------------------------------------

                 Key: LUCENE-1264
                 URL: https://issues.apache.org/jira/browse/LUCENE-1264
             Project: Lucene - Java
          Issue Type: Bug
          Components: Analysis
    Affects Versions: 2.3.1
            Reporter: Benson Margulies


Methods such as 'next' and 'reset' are defined to throw only IOException.

IOException, as one of the older and dustier Java exceptions, lacks a constructor over a 'cause'
exception.

So, if a Tokenizer (for example) uses some complex underlying facility that throws arbitrary
exceptions, the coder has two bad choices: wrap an IOException around some string derived
from the real problem, or throw an unchecked wrapper.

Please consider adding a new checked exception to the signature of these methods  that implements
the 'cause' pattern.



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org


Mime
View raw message