It should not be mandatory to use always use the full resource name when querying a complex feature type

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 should not be mandatory to use always use the full resource name when querying a complex feature type #4

Open nmco opened 6 years ago

nmco commented 6 years ago

App-Schema defined feature types need always to be referenced by their full qualified name ( workspace_prefix:feature_type_name ) even in the context of a particular workspace virtual service. This is a limitation that may prevent INSPIRE full compatibility to be reached.

nmco commented 5 years ago

Pull request: https://github.com/geoserver/geoserver/pull/3092

fernandor777 commented 4 years ago

JIRA ticket: https://osgeo-org.atlassian.net/browse/GEOS-8919