Kathi,

this seems to only affect WFS 2.0 requests made against app-schema types. WFS 1.1 is not affected:
http://bolegweb.geof.unizg.hr:2017/geoserver/ows?service=wfs&version=1.1.0&request=describeFeaturetype&typename=gn:GeographicalName

Kind regards,
Ben.

On 09/08/17 12:28, Ben Caradoc-Davies wrote:
Kathi,

if I request a single type, the response seems better:
http://bolegweb.geof.unizg.hr:2017/geoserver/ows?service=wfs&version=2.0.0&request=describeFeaturetype&typename=proplant:obs_all

I think you have some app-schema types in there. Did any of them specify the WFS schema in schemaURI?

If look at gn:GeographicalName, I see the WFS schema jar import:
http://bolegweb.geof.unizg.hr:2017/geoserver/ows?service=wfs&version=2.0.0&request=describeFeaturetype&typename=gn:GeographicalName

Kind regards,
Ben.

On 09/08/17 10:20, Kathi Schleidt wrote:
Hi Ben,

URL: http://bolegweb.geof.unizg.hr:2017/geoserver/ows?service=wfs&version=2.0.0&request=describeFeaturetype

:)

Kathi


On 08.08.2017 23:17, Ben Caradoc-Davies wrote:
Kathi,

I cannot reproduce this on master with topp:states. What is your GeoServer version, and do you have a URL that reproduces this behaviour for one of the release sample layers?

For example:
http://localhost:8080/geoserver/wfs?service=WFS&version=2.0.0&request=DescribeFeatureType&typename=topp:states&format=gml32

The response I see is a GML 3.2 document that makes no reference to the WFS schema.

Kind regards,
Ben.

On 08/08/17 22:25, Kathi Schleidt wrote:
Hi,

I've been running into problems with the WFS Schema Location returned in DescribeFeatureType.

I've configured GeoServer to return the official xsd, most requests (capabilities, get feature) provide this: xsi:schemaLocation="http://www.opengis.net/wfs/2.0 http://schemas.opengis.net/wfs/2.0/wfs.xsd

However, when I do DescribeFeatureType, I get interesting internal references which end up breaking downstream software:

<xsd:import namespace="http://www.opengis.net/wfs/2.0"; schemaLocation="jar:file:/usr/share/apache-tomcat-8.5.12/webapps/geoserver/WEB-INF/lib/gt-xsd-wfs-16.2.jar!/org/geotools/wfs/v2_0/wfs.xsd"/>

I tried this on various systems, behavior is consistent (and provides nice additional information as to the OS being run as well as the local config! )

Any solutions?

:?

Kathi



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot



_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users





--
Ben Caradoc-Davies <b...@transient.nz>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to