Small correction Andrea: > Hints looks fine, seems to be easily bent to current needs, yet those > hints are general, and do not seem to fit well will the pluggable > nature of data stores (and, as a consequence, the variable nature of > hints), since the class does accept only ClassKey instances (and > ClassKey is package private, so it cannot be instantiated in other > packages). We could keep on using it, if this limitation is removed, > or creating another one, specific for Query hints. You can define additional Hints (ie that are not ClassKey), we have several examples of configuration options that are simple numbers when controlling the time outs and connection pool limits for the referencing module.
Cheers, jody Jody Garnett wrote: > Personally I expected the following: > - to use Hints straight up, not pass them in one at a time... your > setHint method seems to have a side effect? > > Hints hints = new Hints( > Hints.DECIMATION_DISTANCE, new Double(1500.12), > Hints.COORDINATE_SEQUENCE_FACTORY, > "org.geotools.geometry.jts.PackedCoordinateSequenceFactory" > ); > query.setHints( hints ); > > This enables the resuse of factories etc. > ------------------------------------------------------------------------- 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
