|
|
Clifford Harms created an issue |
|
Issue Type: |
|
|---|---|
|
Affects Versions: |
2.7.1.1 |
|
Assignee: |
Unassigned |
|
Attachments: |
org_geoserver_catalog_impl_CatalogImpl.patch |
|
Created: |
19/Aug/15 9:36 PM |
|
Priority: |
|
|
Reporter: |
|
CatalogImpl allows layer names to contain colons. It assumes the string prior to the colon is a workspace, but falls back to assuming that the entire string is a layer name without workspace if the parsed name fails to return a result. CatalogImpl does not implement this behavior for coverage names - coverages with a colon in the name that are not also prefixed with a namespace name fail to return a coverage. This leads to unexpected behavior in some components (i.e. gs-wcs1_0) when it is assumed that a valid layer name is also a valid coverage name. CatalogImpl should implement for coverage names the same type of fallback that it uses for resolving layer names. I’ve attached a patch that implements this behavior, as names with colons in them are strangely a requirement of my organization, and have yet to experience any issues with t. |
|
|
|
This message was sent by Atlassian JIRA (v7.0.0-OD-01-193#70101-sha1:4fc7e3f) |
|
|