|
carl created an issue |
CoverageResource small fix/tweak to correctly detect new coverage/layer |
Issue Type: |
|
---|---|
Affects Versions: |
2.8.3 |
Assignee: |
Unassigned |
Components: |
REST |
Created: |
29/May/16 2:26 AM |
Priority: |
|
Reporter: |
I think there is a small fix than can be done in the isNewCoverage method in org/geoserver/catalog/rest/CoverageResource.java. This is the current implementation: /**
I think that method should also check for empty (not null) metadata and keywords. For example, geoserver manager send those elements as empty tags, so they are parse and created as empty list and not null lists in CoverageInfo object. So with the current implementation, if we try to create a new coverage/layer, only providing name / nativeCoverageName, it’s not recognized as “new” because metadata and keywords are empty list, and not null values, so values of the coverage/layer are not properly set. An easy way to check, if you use this will create and incomplete coverage/layer And this will create a coverage/layer with the values properly set |
This message was sent by Atlassian JIRA (v1000.5.2#72002-sha1:b4422fe) |
|