Re: [Geotools-devel] eating exceptions too early - more crazy thoughts

[Martin D. <mar...@te...>]

Ian Schneider a =E9crit:
> I propose one of the following:
> 1) DataSources undergo rigorous code reviews to evaluate exception
> handling, or
> 2) The DataSourceException constructor is limited to chaining, or
> 3) DataSourceException is replaced by IOException and RuntimeExceptions=
,
> or
> 4) All exception handling be done through an ExceptionHandler=20

I have no strong preference. I vote for all of the following:

1) Keep DataSourceException.

2) Maybe set DataSourceException as a subclass of IOException
    (like IIOException for Image I/O). I lets the decision up
    to you.

3) Reduce the amount of DataSourceException through the use of
    UnsupportedOperationException, IllegalArgumentException etc.
    when it fits. I agree with you that argument checking is probably
    not DataSourceException's job.

	Martin.