As andrea indicated in his last email there is certain amount of hate for the duplication between FeatureSource / FeatureCollection :-) I would like to start stripping abilities out of FeatureCollection in a careful controlled manner.
Today I have my first candidate for removal: - addListener(CollectionListener listener) throws NullPointerException - removeListener(CollectionListener listener) throws NullPointerException Reasons: - AbstractFeatureCollection maintains a list of listeners ... but never fires events to them - indeed I can only find one implementation that looks like it works ... ContentFeatureCollection The idea of issuing events here encourages users to keep a feature collection around and modify it; a case where we want to encourage FeatureSource. Jody ------------------------------------------------------------------------------ _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel