search

geosolutions-it / inspire-issues

This repository works as an aggregator for GeoServer known issues with respect to INSPIRE compliance and support.
https://waffle.io/geosolutions-it/inspire-issues
0 stars 0 forks source link

It is not possible to use more than one endpoint per Geoserver instance #13

Open nmco opened 5 years ago

nmco commented 5 years ago

There is a known bug (https://osgeo-org.atlassian.net/browse/GEOS-4773) that is not solved for more than five years already as Geoserver is creating null prefixes for complex features in virtual services that are used to create multiple endpoints. If a data provider has more than one dataset to be provided via WFS in Geoserver than for each dataset he will need an endpoint (according to Requirement 52 of the Tehnical Guidelines for Inspire Download Services) That endpoint is used as well in the metadata in order for indicate the internet address where it is possible to access that dataset via WFS (actualy the GetCapabilities document). Geoserver is using so called virtual services in order to create multiple endpoints. Unfortunately for complex features (that are in GML 3.2) a WFS request to such an endpoint is providing a GML 3.2 file with null values for prefixes, that makes the GML files unusable. Solving this bug will be the first step that will allow a data provider to serve via WFS one dataset for each XSD schema. If the bug will be fixed the data provider will not be able to serve two or more datasets for the same XSD schema and the data provider will not be able to create stored querries with the same identifier for each dataset, unless the previous two issues will be solved as well.

Workaround The data provider has to instal Geoserver for each dataset. If a data provider has 10 datsets than he will need to install 10 instances of Geoserver, most probably on multiple servers.

nmco commented 5 years ago

Maybe a duplication or direct consequence of #1.