We're updating the issue view to help you get more done. 

REST API writes invalid layergroup configuration to disk when layergroup references non-existent layer

Description

In the REST API, modifying a layergroup to include a reference to a layer name that's not associated with any layer in GeoServer will cause an invalid layergroup to be persisted to the catalog. The in-memory catalog doesn't retain it, leading to a curious case where attempts to update or delete the layergroup (to correct the issue) fail with a "404 Not Found" error and attempts to create a new layergroup in its place fail with a "403 Name already in use" error.

Environment

None

Status

Assignee

Torben Barsballe

Reporter

codehaus

Triage

Fix versions

Affects versions

None

Components

Priority

Medium