lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] Updated: (LUCENE-1264) Use of IOException in analysis component method signatures leads to poor error management
Date Tue, 29 Apr 2008 13:33:56 GMT

     [ https://issues.apache.org/jira/browse/LUCENE-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gavin updated LUCENE-1264:
--------------------------

    Reporter: Benson Margulies  (was: Benson Margulies)

> 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