Gabriel Roldán a écrit :
> Cool. Yet for org.geotools.data stuff I guess we should keep using
> DataStoreException to overcome this limitation as it was created just for
> this reason? (It's actually an IOException with a constructor that receives
> the cause)
I have not looked at DataStoreException, but from the name I would expect that
it has more value than just overcome this limitation? It sound like a good way
to identify exception caused by a DataStore problem, as opposed to exception
caused by some other IO problem. Well, it all depends in which context
DataStoreException are thrown (if the javadoc state that this exception is
thrown in some well identified context, and if we really respect that in the
actual code).
Martin
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
