nmco
commented
5 years ago Ilkka Rinne: See my comment in ""Unique Endpoint per Dataset"" Iurie Maxim 21/4/2017: Not sure if the ""isolated workspaces"" even if will be developed in the next months will solve the problem. The solution proposed must be tested for example by providing with the same Geoserver intance two datasets for the same featureType (i.e.: dataset 1 - geology scale 1:200.000 at national level, dataset 2 = geology of one area at 1:50.000 scale with more details/attributes) with different metadata pointing to different endpoints. Each dataset must be accesible as well trough a strored querry having the same Id, but accessed at different endpoints. Therefore stored querries must not be available at geoserver level, but at workspace level.
For an XSD schema GeoServer is creating by default a workspace, that can be used as an endpoint to be used to request that dataset through WFS or WMS. The problem is that the workspace and the endpoint are inheriting the name of the schema. Therefore with GeoServer it is currently possible to create only one workspace and one endpoint for one XSD schema. This means that if a data provider has more than one datasets that are refering the same XSD schema, then that provider cant use the GeoServer solution, unless he is installing GeoServer on multiple servers with different web addresses (endpoints). As in reality most data providers have more than one dataset (with different metadata) for a XSD schema, they cant use GeoServer. An example is a data provider that has geology for the entire country at 1:200.000 scale and some areas covedered with more details, at 1:50.000 scale.
Workaround Installing Geoserver several times on the same server or on multiple servers. If a data provider has for example five datasets for an XSD schema he will need to have 5 Geoserver instances. More likely nobody will do this in a production environment.