Hi,
While going over errors encountered by an app-schema based WFS service on
Geoserver when testing with teamengine, I noticed that GeoTools currently
encodes any simple attribute (having only a textnode) as a full object. It
is my understanding that the WFS 2.0 standard requires such attributes to
be returned as simple text nodes. The WFS 2.0 standard says that "The
response shall be a text node or a list of element nodes that is the value
of the node pointed to by the valueReference parameter." (section
10.2.4.3). Furthermore, see example GetPropertyValue exchanges in Annex B
(e.g. sections B.4.5 and B.4.7)
Consequently, the following GET (taken from GeoServer's app-schema tests):
?request=GetPropertyValue&version=2.0.0&typename=gsml:MappedFeature&valueReference=gml:name&count=1
should return
<wfs:ValueCollection ...>
<wfs:member>GUNTHORPE FORMATION</wfs:member>
</wfs:ValueCollection>
instead of:
<wfs:ValueCollection ...>
<wfs:member>
<gml:name>GUNTHORPE FORMATION</gml:name>
</wfs:member>
</wfs:ValueCollection>
I expect any change to be breaking, thus I am interested what is the
community's opinion on this issue (i.e. correct encoding of the
GetPropertyValue response). Looking a bit over the code, a "clean"
solution doesn't appear trivial (if the current implementation is the one
expected, I'll probably go for some quick&dirty hack for my local
implementation)
Thank you,
Daniel Urda
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
