Coverage name ignored for new coverages

Description

When CoverageStores are created by setting the file via xml, the creation of the Coverage ignores the given name and uses nativeCoverageName instead.

This is because the name is not set after building the coverage, see here.

Something like the following should be enough to avoid this bug:

  • Before buildCoverage save coverage.getName() to some variable e.g. coverageName

  • After buildCoverage call coverage.setName(coverageName)

Steps to reproduce:

Post rest/workspaces/

Post rest/workspaces/TestWorkspace/coveragestores

Post rest/workspaces/TestWorkspace/coveragestores/TestCoverageStore/coverages

GET rest/workspaces/TestWorkspace/coveragestores/TestCoverageStore/coverages/TestCoverage

=> Results in 404

Environment

None

Activity

Show:
Brad Hards
December 16, 2016, 11:05 AM

In your final POST (to create the coverage), why did you choose `<nativeName>` rather than `<nativeCoverageName>`? I'd like to ensure that I get the required documentation updates into this fix if possible, and understanding what information sources you used might help to make it more useful and relevant.

Christopher Dresel
January 4, 2017, 7:07 AM

Sorry for my late reply. To be honest I don't even know whats the difference between nativeName and nativeCoverageName is.

Jody Garnett
April 10, 2017, 10:35 PM

Retest after rest-api-refresh merge

Assignee

Unassigned

Reporter

Christopher Dresel

Triage

Fix versions

None

Affects versions

Time tracking

0m

Time remaining

1h

Components

Priority

Medium
Configure