David Winslow created GEOS-5055:
-----------------------------------

             Summary: REST API writes invalid layergroup configuration to disk 
when layergroup references non-existent layer
                 Key: GEOS-5055
                 URL: https://jira.codehaus.org/browse/GEOS-5055
             Project: GeoServer
          Issue Type: Bug
          Components: REST
            Reporter: David Winslow
            Assignee: Andrea Aime


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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to