Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=GEOS-142
Here is an overview of the issue:
---------------------------------------------------------------------
Key: GEOS-142
Summary: Store services.xml and catalog.xml in a .geoserver directory?
Type: Improvement
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: GeoServer
Versions:
1.2.0
Assignee: Chris Holmes
Reporter: Chris Holmes
Created: Tue, 6 Apr 2004 7:34 AM
Updated: Tue, 6 Apr 2004 7:34 AM
Environment: all
Description:
I've been thinking it may be a bit weird for us to write our persistance directly inside the webapp, as Jetty just makes a temp directory every time you run it and therefor can't persist for us by default. And I think people could also unknowingly blow away their changes, like when installing a new version of GeoServer.
My current idea is to create a .geoserver directory in the user's home. Maven does the same, so I figure it must not be too hard to do in java. We would store the services.xml and catalog.xml files there. This would make a nice entry point for users to edit their own config files (since looking in WEB-INF is a bit weird, and confused when building from source, and it's in the conf directory). This would have a nice side effect for developers, as building from source would not wipe out the changes you made in the web admin tool (which happens now because it just uses your conf directory, and dropping in the new war over writes the old changes). This would make our nice cite builds not work so well, though I'm sure we could figure out a good solution. I suppose this begs the question of where you put say the shapefiles, as maybe files could be in .geoserver/data ?
---------------------------------------------------------------------
JIRA 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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira