Hi, ECQL has been around for a while and we failed to use it in 2.0.x so far.
I've checked, it seems all the changes required to switch from CQL to ECQL in GeoServer boil down to changing CQL -> ECQL in two files (see attached patch). The assumption is, ECQL is a clean extension so there is no need for the user to know that we actually switched parsers, we can keep on having users hit CQL_FILTER=.... (we just have to document the extra capabilities starting from version x.y.z). The build after that change works fine. I would certainly go for the switch on trunk, what about 2.0.x as well? Wondering if ECQL has been tested enough for a stable series. Is uDig using it already? Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
