Justin Deoliveira wrote:
Currently AbstractResourceCollection doesn;t allow subclasses to throw
any exceptions in openIterator() and closeIterator(). Which makes
sense since the java.util.Collection#iterator() doesnt support any
exceptions. However these methods will undoubetdly be doing IO.
I don't really mind, sure let it throw IOException (or perhaps any
Exception) and we will bundle it up in what ever RuntimeException we are
supposed to throw ... BackingDataStoreException I think?
So should we leave the api as is or let the sublcasses throw IOException;
Change the API, that way your wrapping iterator() method gets to do the
work in one spot, and all the subclasses have less to worry about.
Jody
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
