|
|
Why?
A revamped configuration system wasn't on the roadmap, but the current system makes it difficult to add more than one layer, and a lot of the changes to the layer code also require a new configuration structure.
Proposed implementation
Instead of one property file for all layers I propose a configuration director. All property files in this directory are parsed and layers created directly based on this.
The location of the directory is determined by the environment variable to be named. This idea is modeled on GeoServer's GEOSERVER_DATA_DIR, which is looked up from a (Java) environment variable. Alternatively the value can be specified in web.xml. Lastly, the system will try a default.
The servlet will throw an exception if the directory does not exist or is not readable.
Sign in to add a comment
