It is going to be pretty tricky to arrive at a Set; it may be open ended depending on what factories you are passing in ...When you declare a specific GeometryFactory for example it may need a additional CRSFactory etc...
Do we care? Jody > Andrea Aime ha scritto: >> Jody Garnett ha scritto: >>> If we follow suite; getImplementationHints would return a >>> Map<RenderingHints.Key,Object> of the configuration that was >>> actually used. Ie *everything* (it may be from the global hints, or >>> defaults used by the implementation or whatever...). The fact that >>> some of this configuration stuff comes from a "per query" setHints() >>> method is a detail.... >> >> Ok, I was tring to get too fancy. I re-updated the page to have >> FeatureSource.getSupportedHints() instaed. Stateless, simpler. >> >> http://docs.codehaus.org/display/GEOTOOLS/Add+hints+support+to+Query+object >> >> >> What do you think? If no one has objections, > > Updated it again, Jody made me notice the > FeatureSource.getSupportedHints() should return a Set (in trunk, it > will be a set of RenderingHints.Key, on 2.4.x just a Set). > > 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
