Uploaded image for project: 'GeoServer'
  1. GEOS-5055

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

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Medium
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: 2.12-beta
    • Component/s: REST
    • Labels:
      None

      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.

        Attachments

          Activity

            People

            • Assignee:
              tbarsballe Torben Barsballe
              Reporter:
              harrison.grundy codehaus (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: