Per list suggestion, here's a page summarizing thoughts on SQLEncoder porting-to-geoapi-filters questions.
http://docs.codehaus.org/display/GEOTOOLS/SQLEncoder+Upgrade+to+GeoAPI+Filters If you're interested/care, please peruse and let me know what you think about package/class renaming. I'll finalize stuff in the next few days and then commit so someone can take a gander at the code itself. It's worth noting that I *DON'T* think we need to solve the FilterCapabilities problems right now. That's a big one, and will get solved eventually. So don't get hung up on FilterCapabilities right now. Feel free to discuss and all, but I think my recent tweaks to the current internals of FilterCapabilities are good enough to make *this little piece* work just fine. --saul ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
