Looking at the situation here is what I found (which really just sums up
everyones findings).
2.0.x:
WFS 1.1/GML3 duplicates any attributes that come from abstract feature type
like name and description. Found the bug and committed the fix on 2.0.x.
2.1.x:
WFS 1.0 GetFeature is inconsistent with regard to it's DescribeFeatureType
output. Or vice versa. The reason is that historically GML2 output always
maps these attributes to the app schema namespace, unless running in cite
compliant mode in which it maps them to the gml namespace. Whereas the DFT
output always maps them to gml. A straight forward and short term fix would
be to do a check in the DFT for GML2 and non cite compliance. If that
condition holds then we don't map the attributes to gml.
A better longer term fix would be to make this behaviour configurable for
both WFS 1.0 and WFS 1.1 adding a config option to GMLInfo to control the
behaviour for the various versions. Making the defaults mirror the behaviour
of the individual versions today. That is in GML2 we would by default map
the attributes to the app schema namespace, and in GML3 the default would be
not to map them to the app schema namespace. I started on a patch for this
and it should be pretty straight forward, but would need a
general consensus and review in order to get it into the 2.1.0 release.
On Sun, Mar 13, 2011 at 7:04 PM, Ben Caradoc-Davies
<ben.caradoc-dav...@csiro.au> wrote:
> Rini saw different behaviour (different encoded name) in WFS 1.1 and WFS
> 1.0.
>
>
> On 12/03/11 01:20, Andrea Aime wrote:
>
>> (the specific test is wfs:wfs-1.1.0-Basic-GetFeature-tc29.4)
>> Ah btw, the WFS 1.0 tests did run fine, no failures there
>>
>>
> --
> Ben Caradoc-Davies <ben.caradoc-dav...@csiro.au>
> Software Engineering Team Leader
> CSIRO Earth Science and Resource Engineering
> Australian Resources Research Centre
>
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
