[Geoserver-devel] [geoserver-devel] WFS cascading

Jukka_Rahkonen · October 30, 2014, 10:53am

Hi,

I believe (don’t know, only guess) that Geoserver is implementing version negotiation as it is written to the standards, which, BTW, would be good to download from the OGC web site and keep at hand. This is a beginning of the WFS 1.1.0

6.2.4 Version number negotiation

An OWS Client may negotiate with a Service Instance to determine a mutually agreeable specification version. Negotiation is performed using the GetCapabilities operation [sec. 13] according to the following rules.

All Capabilities XML must include a protocol version number. In response to a GetCapabilities request containing a version number, a web feature service must either respond with output that conforms to that version of the specification, or negotiate a mutually agreeable version if the requested version is not implemented on the server. If no version number is specified in the request, the server must respond with the highest version it understands and label the response accordingly

….

Thus, if you could make cascading to work by giving version number explicitly then it should have worked also without version number if the version negotiation is done correctly between Geoserver as client and the remote WFS as a server. However, for my mind it is much better to give the version number and not to trust on the result of negotiations. The documentation at http://docs.geoserver.org/stable/en/user/data/cascaded/wfs.html could really mention something about version.

-Jukka Rahkonen-

···

Räder, Michael wrote:

Thanks for your answer.

It was my problem, because I define the GetCap only to the http://…/…? and not the complete Request for GetCap and it Versions.

It would be better for the User/Admninistrator that this URL don’t work and explain that there are differences because of versions.

What Version is the default for geoserver? 1.1.0?

Mit freundlichen Grüßen

Im Auftrag

Michael Räder

Nationalpark-Verwaltung Niedersächsisches Wattenmeer
Virchowstr. 1 / 26382 Wilhelmshaven
Tel.: +49 (0) 4421 911 295 / Fax.: +49 (0) 4421 911 280

Email: michael.raeder@…3245…

║ [MDI - NI] ║ [NLPV] ║ [MDI - DE] ║

Von: Rahkonen Jukka (Tike) [mailto:jukka.rahkonen@…1245…]
Gesendet: Donnerstag, 30. Oktober 2014 10:41
An: Räder, Michael; ‘geoserver-devel@lists.sourceforge.net’
Betreff: Re: [geoserver-devel] WFS cascading

Hi,

At least and maybe only those which are compulsory for WFS servers: XMLSCHEMA for WFS 1.0.0, GML3 for WFS 1.1.0 and GML 3.2 for WFS 2.0.0.

WFS 1.0.0:

The only mandatory output format in response to a DescribeFeatureType operation is XML Schema, denoted by the value XMLSCHEMA for the outputFormat attribute. Other vendor specific formats are also possible, but they must be advertised on the capabilities document [sec. 12].

WFS 1.1.0

The only mandatory output in response to a DescribeFeatureType request is a GML3 application schema defined using XML Schema. However, for the purposes of experimentation, vendor extension, or even extensions that serve a specific community of interest, other acceptable output format values may be advertised by a WFS service in the capabilities document [clause 13]. The meaning of such values in not defined in the WFS specification. The only proviso in such cases is that WFS clients may safely ignore outputFormat values that they do not recognize.

WFS 2.0.0

Shall include the value “application/gml+xml; version=3.2”. May include any other string or MIME type that the server supports including previous version of GML.

If the remote WFS does not support those it is obviously wrong, if it does but Geoserver does not recognize the format it is a bug in Geoserver.

-Jukka Rahkonen-

Räder, Michael wrote:

Failure for the new wfs cascading store : geoserver 2.6 (27.10.2014)

Caused by: java.lang.IllegalArgumentException: Client does not support any of the server supported output formats for DESCRIBE_FEATURETYPE

Which formats geoserver can use? Can’t find information in the documentation.

Best regards Michael