On Thu, Mar 10, 2011 at 6:16 PM, Justin Deoliveira <jdeol...@opengeo.org> wrote: > > 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.
I see it happening on both GML2 and GML3, but you're right, the behavior is different. GML2: DescribeFeatureType does not list the "name" attribute (it did in 2.0.2) but the GetFeature output says <topp:name>the name</topp:name> so it is inconsistent, it's actually generating gml that would not validate GML3: DescribeFeatureType does not list the "name" attribute but the output uses gml:name (in 2.0.2 it used topp:name in both) 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
