FeatureCollection should be encoded with multiple featureMember elements not 
one featureMembers element to support xlink:href
-----------------------------------------------------------------------------------------------------------------------------

                 Key: GEOT-3046
                 URL: http://jira.codehaus.org/browse/GEOT-3046
             Project: GeoTools
          Issue Type: Bug
          Components: ext xml-xsd
    Affects Versions: 2.6.4, 2.7-M0
            Reporter: Ben Caradoc-Davies


GeoTools (and thus GeoServer) encodes a FeatureCollection as (for example):

{code}
<wfs:FeatureCollection>
<gml:featureMembers>
<gsmlMappedFeature gml:id="mf.1" />
<gsmlMappedFeature gml:id="mf.2" />
<gsmlMappedFeature gml:id="mf.3" />
</gml:featureMembers>
</wfs:FeatureCollection>
{code}

In this skeleton, the features are empty, but if they are encoded inline, it is 
possible that, because of associations, a feature (e.g. mf.3) might have been 
already been encoded inline as a property of an earlier feature before it is to 
be returned as a top-level feature in its own right. In this case, the feature 
should be encoded as an internal xlink:href link on the enclosing property 
type, because gml:id's cannot be duplicated in a document. This is only 
possible if featureMember is used. The response then becomes:

{code}
<wfs:FeatureCollection>
<gml:featureMember>
<gsmlMappedFeature gml:id="mf.1">
...
<gsmlMappedFeature gml:id="mf.3" />
...
</gsmlMappedFeature
</gml:featureMember>
<gml:featureMember>
<gsmlMappedFeature gml:id="mf.2" />
</gml:featureMember>
<gml:featureMember xlink:href="#mf.3" />
</wfs:FeatureCollection>
{code}


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to