As I go through and hunt down bugs in the DataUtilities methods for manipulating FeatureType and Query information I am reminded of the purpose of this class - to capture common functionality that was "missing" from the library (or hard to implement which amounts to the same thing).
Now back in 2003 when I was too intimidated by all the crazy people on this list to effect much change I hid all this functionality in DataUtilities - usually assuming I was too dense to know the correct way to use the library. Now I know better.... What do you guys think about moving some of this functionality to methods; on the objects we are manipulating. The query manipulation code could move to methods on DefaultQuery; DefaultQuery already has a constructor that accepts a Query (as far as I know only uDig would be silly enough to create its own query implementation). What do you think? Jody ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
