It is common that data providivers are managing spatial databases that are based on multiple INSPIRE data themes, as for example a topographical map containing roads, rivers, lakes, inhabited places, geogrpahical names, administrative units etc. Having common metadata, all these "layers" are part of the same dataset. Becauase Geoserver is creating one workspace and one virtual service (endpoint) for each XSD schema, in order to access this dataset virtual services cant be used.Therefore by using Geoserver it is not possible to provide access via WFS to more than one dataser based on multiple INSPIRE data themes. If a data provider would need to provide access to two such datasets, then the only solution is to install the second instance of geoserver.
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 on multiple servers with 10 different endpoints.
It is common that data providivers are managing spatial databases that are based on multiple INSPIRE data themes, as for example a topographical map containing roads, rivers, lakes, inhabited places, geogrpahical names, administrative units etc. Having common metadata, all these "layers" are part of the same dataset. Becauase Geoserver is creating one workspace and one virtual service (endpoint) for each XSD schema, in order to access this dataset virtual services cant be used.Therefore by using Geoserver it is not possible to provide access via WFS to more than one dataser based on multiple INSPIRE data themes. If a data provider would need to provide access to two such datasets, then the only solution is to install the second instance of geoserver.
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 on multiple servers with 10 different endpoints.