The following has come up three times this week - the fact that geotools 
trunk has not completed its migration to Filter. Andrea and Gabriel 
volunteered some months ago - but we did not get a suitable work party 
together to make it happen.

Here are the three cases:
- aggregate functions do not work (and have not since 2.3) - this 
prevents uDig trunk from having a style editor, and prevents the SLD 
generator from being happy
- "problem with adding features" email thread on geotools-users - 
basically FeatureID is not stable, to fix this Jesse makes his own 
FidFilter and updates the internal Set<String> after the commit. This 
FidFilter is just a GeoAPI filter so a lot of the geotools datastores 
die on it
- casting Filter.INCLUDES and Filter.EXCLUDES as per Andrea's original email

Does anyone have anything else for this list? Chances are this stuff 
will trip us up in the code sprint.
Jody

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to