|
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.
schemas/gml/2.1.2/feature.xsd imports xlinks from the same catalog (schemas/gml/2.1.2/xlinks.xsd).
It also includes geometry.xsd (schemas/gml/2.1.2/geometry.xsd)
This file imports xlinks from “…/…/xlink/1.0.0/xlinks.xsd” (schemas/xlink/1.0.0/xlinks.xsd)
These two separate imports makes the WFS-client go bananas.
It does not allow that different versions are imported at different places and both are declaring targetNamespace=“http://www.w3.org/1999/xlink”.
We can change to either schemas/xlink/1.0.0/xlinks.xsd (xlinks.xsd v3.0b2 2001-07) or schemas/gml/2.1.2/xlinks.xsd (xlinks.xsd v2.1.2 2002-07) and the client is happy.
The difference between these versions is only that the “use” attribute is added on attribute-nodes.
So, the problem is not the version but the mix of versions.
|
