|
I noticed two issues with specifying a layer name as part of a virtual service that both seemed to be caused by line 63 in org.geoserver.ows.OWSHandlerMapping not providing a workspace qualified layer name:
if (catalog.getLayerByName(first) != null) {
-
When JDBC Configuration is enabled, the request will return a 404 response if the layer name is used in more than one workspace. This is because DefaultCatalogFacade returns the first layer if there is more than one layer with the same name so this check still passes but JDBCCatalogFacade returns null in that situation so it doesn’t pass this check.
-
If a layer name exists but is not in the specified workspace, the request will be handled as if a layer was not provided in the request (e.g., “test/missing/wms” will be handled as “test/wms” if the layer “missing” exists but not in the “test” workspace). This is because LocalWorkspaceCallback uses the workspace qualified layer name when setting the LocalPublished value and just ignores the layer name if it doesn’t exist, allowing the request to continue with only the LocalWorkspace set.
|
