Yay! Let me know if you need any help.
> * PropertyIsNil
>
> Filter (FES) 2.0 adds a new filtering construct named PropertyIsNil. To be
> honest I am still a bit fuzzy on what this is actually supposed to do.
> However I did get some clarification from wfs-dev list:
>
> > assume you have a GML feature type which has a property p where the
> > property element is declared with minOccurs="0" and nillable=true.
> > PropertyIsNull results in true, if the WFS would return the feature without
> > any property element <tns:p>.
> > PropertyIsNil results in true, if the WFS would return the feature with a
> > property element <tns:p xsi:nil='true'>. This can be refined using the
> > nilReason parameter.
>
> And as it turns out i completely misinterpreted the spec... so my
> implementation of PropertyIsNil doesn't match that at all :)
Been there done that.
> I am tempted to simply just have PropertyIsNil be an alias for PropertyIsNull
> at this point... and when someone has a mandate to implement it properly they
> can do so. Thoughts?
I would rather do that; and just be up front we don't have PropertyIsNull
available. I think we could implement the difference; but it is not likely to
come up unless you have application-schema in the mix.
> * ExtendedOperator
>
> Filter 2.0 also adds the notion of extended operators. Which are essentially
> a way to extend filter with new constructs (just like functions) but by
> actually extending the filter language. For example you could add a new type
> of filter with something like this:
>
> <Filter>
> <Function name="foobar">
> ...
> </Function>
> </Filter>
>
> What extended operators allow you to do is the following:
>
> <Filter>
> <myns:foobar>
> ...
> <myns:/foobar>
> </Filter>
>
>
> So really they are just syntactic sugar.
Yum; sugar. Is there any reason not to just use FilterFunctionFactory and have
it be an open for the user which way they want to write things up?
> There is no default implementation, what i did was actually come up with an
> implementation in geoserver that allowed one to write extended operators in
> its templating language freemarker.
Not sure I get how the tempting language fits in?
> * WFS 2.0/FES 2.0 Object model and bindings
>
>
>
> Not much to say here... I added new emf objects models for wfs 2.0 and fes
> 2.0. And implemented all the bindings for them in the xsd modules. Patch
> attached to these issues:
>
> http://jira.codehaus.org/browse/GEOT-3541
> http://jira.codehaus.org/browse/GEOT-3542
>
> For those who like browsing patches on github i pushed all these 5 patches
> onto a new "staging" branch in my github repo:
>
> https://github.com/jdeolive/geotools/tree/wfs2_staging
>
> Feedback much appreciated.
I will review on Monday (australia time); thanks for the hard work Justin!
Jody
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2dcopy2
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
