Tim Englich ha scritto: > Hello Jesse, > > that's the Problem. There is no test that fails. > The WFSCapabilties were read. But the Process which determine which part of > the Filter is PreFilter and which is PostFilter always say that it is all > PostFilter. > I take a look at the Algorithm which do that an I think that there are som > Capabilities required which are not supported by WFSFilterCapabilities. > > Also when you have tests which do Requests whith Filter in it will work > because the filtering work will be done at the client in the postprocess.
I have a hunch.. may it be that wfs datastore declares the filter capabilities only the old way (declaring old filter capabilities) and not the new way (or vice versa, good datastores are declaring filter capabilities both ways these days)? If so, no wonder no filter gets encoded and everything ends up in the post filters Cheers Andrea ------------------------------------------------------------------------- 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 Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
