Hi, today I was looking into a GeoServer GetFeatureInfo failure happening in some odd condition and found out the failure was due to the code using FilteringFeatureCollection, which is not a SimpleFeatureCollection.
I spotted three classes so far that have not been migrated to SimpleFeatureCollection, org.geotools.feature.collection.DecoratingFeatureCollection and its two subclasses, FilteringFeatureCollection and MaxFeaturesFeatureCollection. Mumble... not sure what to do with them? Should they be switched too? Wondering how many other dormant "bombs" we have in the code base Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
