I think the OGC changed some of this stuff, and I am not sure which one
geoserver uses.

Have a look at http://www.opengeospatial.org/blog/1597and let me know if it
agrees with your experience. It could be either your client or geoserver
needs to transition to official w3c xlink 1.1 Schema.
On Fri, Aug 21, 2015 at 6:56 AM Olle Markljung <[email protected]> wrote:

> Hello
>
>
>
> We're experiencing problems with XSD validation from a WFS-client when it
> is trying to use the info from DescribeFeatureType.
>
> I.e.
> http://localhost:8080/geoserver/topp/wfs?service=WFS&version=1.0.0&request=DescribeFeatureType&typeName=topp%3Astates
>
>
>
> The problem seems to be different includes of xlinks.xsd.
>
> http://localhost:8080/geoserver/schemas/gml/2.1.2/feature.xsd imports
> xlinks from the same catalog
> http://localhost:8080/geoserver/schemas/gml/2.1.2/xlinks.xsd.
>
> It also includes geometry.xsd (
> http://localhost:8080/geoserver/schemas/gml/2.1.2/geometry.xsd)
>
> This file imports xlinks from "../../xlink/1.0.0/xlinks.xsd" (
> http://localhost:8080/geoserver/schemas/xlink/1.0.0/xlinks.xsd)
>
>
>
> These two separate imports makes the WFS-client go bananas.
>
> Likely due to the fact that they are of different versions.
>
>
>
> If we alter geometry.xsd (
> https://github.com/geoserver/geoserver/blob/master/src/main/src/main/resources/schemas/gml/2.1.2/geometry.xsd#L10)
>
>
> to import xlinks.xsd from the same catalog as in feature.xsd everything is
> peachy.
>
>
>
> Does anyone know why two different versions are imported?
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
-- 
--
Jody Garnett
------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to