Hmm... I am unaware of anything we did to explicitly change this behaviour.
It was my understanding that gml3 always maps an attribute named "name", to
gml:name. Although with gml 2 this is configurable. WHat do the
corresponding GetFeature outputs look like? Are they consistent with the
DescribeFeatureType schema?
I think an option to control this is fine... we just need to isolate what
the change was.
On Thu, Mar 10, 2011 at 4:16 AM, Andrea Aime
<andrea.a...@geo-solutions.it>wrote:
> Hi,
> GeoServer 2.1.x changed behavior compared to 2.0.2 when it comes to
> handling the
> GML built in attributes for simple features: 2.0.2 used to report "name" in
> the feature
> type own namespace, but 2.1.x is instead assuming "name" is in the gml
> namespace
> instead. Compare the 2.1.x result:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:cite="http://www.opengeospatial.net/cite";
> xmlns:gml="http://www.opengis.net/gml";
> xmlns:it.geosolutions="http://www.geo-solutions.it";
> xmlns:nurc="http://www.nurc.nato.int"; xmlns:sde="http://geoserver.sf.net";
> xmlns:sf="http://www.openplans.org/spearfish";
> xmlns:tiger="http://www.census.gov";
> xmlns:topp="http://www.openplans.org/topp"; elementFormDefault="qualified"
> targetNamespace="http://www.openplans.org/topp";>
> <xsd:import namespace="http://www.opengis.net/gml";
> schemaLocation="http://localhost:8080/geoserver/schemas/gml/3.1.1/base/gml.xsd"/>
> <xsd:complexType name="polygons_5Type">
> <xsd:complexContent>
> <xsd:extension base="gml:AbstractFeatureType">
> <xsd:sequence>
> <xsd:element maxOccurs="1" minOccurs="0" name="wkb_geometry"
> nillable="true" type="gml:GeometryPropertyType"/>
> <xsd:element maxOccurs="1" minOccurs="0" name="date"
> nillable="true" type="xsd:date"/>
> <xsd:element maxOccurs="1" minOccurs="0" name="test"
> nillable="true" type="xsd:string"/>
>
> <xsd:element maxOccurs="1" minOccurs="0" name="test2"
> nillable="true" type="xsd:string"/>
> </xsd:sequence>
> </xsd:extension>
> </xsd:complexContent>
> </xsd:complexType>
> <xsd:element name="polygons_5" substitutionGroup="gml:_Feature"
> type="topp:polygons_5Type"/>
> </xsd:schema>
>
>
> with the 2.0.2 result:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> xmlns:cite="http://www.opengeospatial.net/cite";
> xmlns:gml="http://www.opengis.net/gml";
> xmlns:it.geosolutions="http://www.geo-solutions.it";
> xmlns:nurc="http://www.nurc.nato.int"; xmlns:sde="http://geoserver.sf.net";
> xmlns:sf="http://www.openplans.org/spearfish";
> xmlns:tiger="http://www.census.gov";
> xmlns:topp="http://www.openplans.org/topp"; elementFormDefault="qualified"
> targetNamespace="http://www.opengeospatial.net/cite";>
> <xsd:import namespace="http://www.opengis.net/gml";
> schemaLocation="http://localhost:8080/geoserver_202/schemas/gml/3.1.1/base/gml.xsd"/>
> <xsd:complexType name="polygons_5Type">
> <xsd:complexContent>
> <xsd:extension base="gml:AbstractFeatureType">
> <xsd:sequence>
> <xsd:element maxOccurs="1" minOccurs="0" name="name"
> nillable="true" type="xsd:string"/>
> <xsd:element maxOccurs="1" minOccurs="0" name="wkb_geometry"
> nillable="true" type="gml:GeometryPropertyType"/>
> <xsd:element maxOccurs="1" minOccurs="0" name="date"
> nillable="true" type="xsd:date"/>
>
> <xsd:element maxOccurs="1" minOccurs="0" name="test"
> nillable="true" type="xsd:string"/>
> <xsd:element maxOccurs="1" minOccurs="0" name="test2"
> nillable="true" type="xsd:string"/>
> </xsd:sequence>
> </xsd:extension>
> </xsd:complexContent>
> </xsd:complexType>
> <xsd:element name="polygons_5" substitutionGroup="gml:_Feature"
> type="cite:polygons_5Type"/>
> </xsd:schema>
>
>
> This is breaking applications relying on DescribeFeatureType to discover
> the
> available attributes that were working with 2.0.x.
>
> As far as I can see there is no flag that can be set, we just switched hard
> to the
> new behavior.
>
> I already had one company I'm following switch back to 2.0.x because of
> this...
> not nice. At the very least this behavior should be admin configurable
> imho.
>
> Opinions?
>
> Cheers
> Andrea
>
> --
> -------------------------------------------------------
> Ing. Andrea Aime
> GeoSolutions S.A.S.
> Tech lead
>
> Via Poggio alle Viti 1187
> 55054 Massarosa (LU)
> Italy
>
> phone: +39 0584 962313
> fax: +39 0584 962313
> mob: +39 333 8128928
>
> http://www.geo-solutions.it
> http://geo-solutions.blogspot.com/
> http://www.youtube.com/user/GeoSolutionsIT
> http://www.linkedin.com/in/andreaaime
> http://twitter.com/geowolf
>
> -------------------------------------------------------
>
>
> ------------------------------------------------------------------------------
> 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
>
>
--
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
