Your are right here, but 1) This breaks the client code 2) The implemeters of FeatureCollection currently throw a runtime exception in such situations (seen in ContentFeatureCollection), you have to rewrite these methods too.
The biggest question is 1) regarding to applications in user space, their apps will not work after switching to geotools 2.7. Quoting Andrea Aime <[email protected]>: > Hi, > looking at the feature collection and feature iterators interfaces again > I'm seeing another serious design mistake: they don't throw IOException > anywhere. > > This is not sane imho, grabbing a collection, getting the feature > iterator, iterating over the features are all occasions in which > you hit file, network or database access: they should throw > checked exceptions imho. > > What do you think? We're still in time to fix this blunder before > 2.7.0 is released. > > Cheers > Andrea > > -- > Andrea Aime > OpenGeo - http://opengeo.org > Expert service straight from the developers. > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
