You could also have a method on FeatureSource to report back the hints that were used by the last getFeaures() request. The motivation here is this; the major driver for this to use a FeatureFactory. Cheers, Jody > Jody Garnett ha scritto: >> I see, you are expecting an implementation to be passed in. >> >> Sometimes (I am thinking referencing here) the implementation >> provided really is just a hint; depending on the data it may not be >> suitable ... at which point factory finder madness kicks in and they >> search for a "good" implementation. > So you're telling me the only sane way to report supported hints > is to do so in the returned FeatureCollection, after FeatureSource > has had the possibility to process the hints? > I ask because none of the hints I'm thinking about and that I will > try to implement support for in the next months are this complex. > > Cheers > Andrea
------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
