[Geoserver-devel] [jira] Created: (GEOS-4705) changing the file/url of an existing coverageStore via REST is not immediately affected until a config reload

changing the file/url of an existing coverageStore via REST is not immediately affected until a config reload
-------------------------------------------------------------------------------------------------------------

                 Key: GEOS-4705
                 URL: https://jira.codehaus.org/browse/GEOS-4705
             Project: GeoServer
          Issue Type: Bug
          Components: REST, WMS
    Affects Versions: 2.1.1, 2.1.0
         Environment: windows XP, tomcat 6
            Reporter: Ivan Price
            Assignee: Andrea Aime
            Priority: Minor

issusing a rest request to change the URL of an existing layer like this:

curl -u admin:xx -v -XPUT -H "Content-type: text/xml" -d "<coverageStore><url>file:C:\images\image.tif</url></coverageStore>" http://localhost:8080/geoserver/rest/workspaces/xx/coveragestores/yy.xml

should result in subsequent requests to that layer rendering the new file, however in version 2.1.x the old file continues to be served until a server reload is issued (via REST or in the UI).

interestingly, if the original request included a change to the <description> parameter the store is automatically refreshed and subsequent requests render the new file.. so it may be that whatever is triggered there should be triggered for requests changing the URL also?

so for example the following works as expected (thanks to <description>), as long as description is different to before:

curl -u admin:xx -v -XPUT -H "Content-type: text/xml" -d "<coverageStore><enabled>true</enabled><description>12345</description><url>file:C:\images\image.tif</url></coverageStore>" http://localhost:8080/geoserver/rest/workspaces/xx/coveragestores/yy.xml

email thread for this is here:

http://osgeo-org.1803224.n2.nabble.com/redefine-source-file-for-a-coverage-via-REST-needs-server-config-reload-tt6664289.html#none

cheers !

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira