Add some sort of self configuring data stores to GeoServer
----------------------------------------------------------
Key: GEOS-2289
URL: http://jira.codehaus.org/browse/GEOS-2289
Project: GeoServer
Issue Type: New Feature
Components: Configuration
Reporter: Andrea Aime
Assignee: Andrea Aime
Fix For: 2.0.x
Another popular FOSS4G 2008 request was some sort of self configuration, in terms of specifying a folder where people can drop new shapefiles to be configured, or a database in which they drop new tables, and so on.
Without going into the development of a full fledged ingestion engine, a simple way to achieve that would be marking a data store (or a coverage store, when we have one) as self configuring, have geoserver pool it for feature types every x seconds, if any new one pops up in the list, have it automatically configured, if a type disappears, auto-remove it. The drill should be actually similar to the mass configuration, with the user specifying a few defaults such a fallback srs, default styles, default bounds should the layer miss any of those information.
--
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