lucene-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dawid Weiss <>
Subject Re: Excessive use of IOException without proper documentation
Date Sun, 04 Nov 2012 20:52:17 GMT
> There is a tremendous difference. I have possibility at compile time to
detect whether an IOE came from Lucene or some other IO related action.

I agree with Shai -- there are just as many (or more) reasons not to create
custom exception classes and just reuse existing classes with known
semantics or propagate the original exception without wrapping it.

If you need to know exactly what caused the error then it's really your use
case and you'll have to live with bloated code. For most people IOException
is sufficient -- something related to I/O went wrong, that's it. These are
basically different extreme viewpoints of looking at the same code, there
is no right or wrong (regardless of the excellent references you provide).


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message