Re: [Geoserver-devel] GeoServer 2.0.2 release

[Andrea Aime]

victor....@csiro.au ha scritto:

Hi Andrea,

Thanks heaps :)

I think the only outstanding issue with wfs1.1.0 now is the following. I will 
proceed with wcs then and come back to wfs1.1.0 :)

The missing </xs:schema> was resolved when I rebuilt the CITE testing tool.


Request d1e27153_1:
   Method: GET
   URL: 
http://localhost:8080/geoserver/wfs?service=WFS&version=1.1.0&request=GetFeature&featureid=Entit%C3%A9G%C3%A9n%C3%A9rique.fid--658fbe8d_128a4e8078b_-7fa7
   Response from parser p:XMLValidatingParser.GMLSF1:

        Validation warning:
  SchemaLocation: schemaLocation value = 'http://www.opengis.net/wfs 
http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd  
http://localhost:8080/geoserver/wfs?service=WFS&version=1.1.0&request=DescribeFeatureType&typeName=sf%3AEntit%E9G%E9n%E9rique'
 must have even number of URI's.
Validation error:
  cvc-complex-type.2.4.a: Invalid content was found starting with element 
'sf:description'. One of 
'{"http://cite.opengeospatial.org/gmlsf":attribut.Géométrie}' is expected.
1 validation error and 1 warning detected.

Messages from parser p:XMLValidatingParser.GMLSF1:

I've attached the response I get from GeoServer.

The Eclipse validator is also complaining about the document contents,
and nicely reports the line at which that happens, which is, line 80!
By just looking at the response I thought it was ok, but an import
in the middle of the document among type and elements looks out of place
to me. Excerpt from the document:

  <xsd:simpleType name="IntRangePropertyType">
    <xsd:restriction base="xsd:integer">
      <xsd:minInclusive value="0" />
      <xsd:maxInclusive value="99" />
    </xsd:restriction>
  </xsd:simpleType>
  <xsd:import namespace="http://www.opengis.net/gml";

Yeah, managed to reproduce the issue. For my limited knowledge of XML schema the bug is an actual one. schemaLocation="http://localhost:8080/geoserver/schemas/gml/3.1.1/base/gml.xsd"; />

  <xsd:complexType name="EntitéGénériqueType">
    <xsd:complexContent>
      <xsd:extension base="gml:AbstractFeatureType">
        <xsd:sequence>

Ben, does it ring a bell for you? Is it possible that some recent
app-schema related changes caused this behavior?

Cheers
Andrea


--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

schema.xsd
Description: XML document

------------------------------------------------------------------------------


_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel