Hi again; I reviewed patrick's patch (and test case).
It adds two new parameters which I documented here:
- http://docs.geotools.org/latest/userguide/guide/library/data/wfs.html
He had only hooked this up for WFS 1.0. I have hooked up wfs strategy up for
wfs 1.0 and wfs 1.1; however filter compliance level is only hooked up for wfs
1.1. Gabriel do you think you could help me hook up filter compliance to wfs
1.1 datastore?
Related issue:
- https://jira.codehaus.org/browse/GEOT-3151
- https://jira.codehaus.org/browse/UDIG-1673
--
Jody Garnett
On Tuesday, 12 April 2011 at 12:15 PM, Jody Garnett wrote:
> On Monday, 11 April 2011 at 8:42 PM, Joaquín Rodriguez-Guerra Urcelay wrote:
> > I added the details to the bug report :)
> Thanks
> > I need to understand better FilterEncodingPreProcessor, but after the test
> > I did the other day, if we have a a filter of the form: and( id( fids ),
> > anything .... ),
> > we can use the low comppliance visitor to extract the anything filter, and
> > the high comppliance visitor to extract the fid filter, right?
> That is my sincere hope; I am going to check if a co-worker is free to add an
> extra parameter to wfs datastore so we can control how the
> FilterEncodingPreProcessor is constructed.
>
> Jody
>
>
------------------------------------------------------------------------------
Benefiting from Server Virtualization: Beyond Initial Workload
Consolidation -- Increasing the use of server virtualization is a top
priority.Virtualization can reduce costs, simplify management, and improve
application availability and disaster protection. Learn more about boosting
the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
