GeoServer 2.0 does not respond to schema changes after restart
--------------------------------------------------------------
Key: GEOS-3062
URL: http://jira.codehaus.org/browse/GEOS-3062
Project: GeoServer
Issue Type: Bug
Components: Configuration
Reporter: Andrea Aime
Assignee: Justin Deoliveira
Fix For: 2.0-beta2
Looking into the ResourcePool code feature types are cached.
In 1.7.x all the caches were wiped out on "apply", but this is not happening anymore in 2.0.x. I guess a reload could be forced by going to the layer config and saving it again (this might force a catalog update event on that type) but does not look like a very natural solution. Restarting GeoServer is not an option in production.
Possible alternatives UI wise:
- have a global "cache cleanup" button that wipes out all the caches around (the resource pool one, but also the external graphics one in the renderer)
- have a button in each layer config that forces its specific caches to be wiped out (but then, we'd need one for stores, for external graphics, maybe for wfs schemas as well?)
The same should be exposed via RESTConfig (a way to reload the catalog/wipe out the caches).
Mint that I recently added a "reload button" in the dev toolbar, but that toolbar is not giong to be visible when Wicket is switched to the production profile.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira