I was thinking about saving today ... as I look at a confluence install.
It seems that we should not assume access to the file system?
They make use of two things:
- edit the confluence-init.properties file in /WEB-INF/classes to indicate a writeable directory (writeable by the server)
- the ability to upload a zip file
I am not sure if either of these is suitable for GeoServer, or how we are supposed to manage shapefiles? Perhaps the best we could do is a config option saying the base url name? This would harm performance (File based access is faster), but it would allow GeoServer to work as a proper war.
Opps reading forward they say the confluence-init.properties file does not work for a pure WAR installation.
Loks like they set up a bit of a search (lets recast this in terms of GeoServer):
1. System properties (ie start the application with -Dgeoserver.home=/path/to/your/geoserver/home
2. geoserver-init.properties (ie edit a file after the war has been unziped by servlet)
3. Servlet context (customize the web.xml deployment descriptor to include a <context-param> called geoserver.home
Apparently some application servers will let you play with System properties, or context params
Thanks a ton for this report Jody - I was definitely thinking that
modeling after confluence would be the way to go. The way they do it
seems quite sane to me. Eventually it could be nice to also persist to
a database, but I think for a start we should just model how they do
things. Perhaps add this as a comment to the geoserver_home jira task?
Quoting Jody Garnett <jgarnett@anonymised.com>:
I was thinking about saving today ... as I look at a confluence
install.
It seems that we should not assume access to the file system?
They make use of two things:
- edit the confluence-init.properties file in /WEB-INF/classes to
indicate a writeable directory (writeable by the server)
- the ability to upload a zip file
I am not sure if either of these is suitable for GeoServer, or how we
are supposed to manage shapefiles? Perhaps the best we could do is a
config option saying the base url name? This would harm performance
(File based access is faster), but it would allow GeoServer to work
as a
proper war.
Opps reading forward they say the confluence-init.properties file
does
not work for a pure WAR installation.
Loks like they set up a bit of a search (lets recast this in terms of
GeoServer):
1. System properties (ie start the application with
-Dgeoserver.home=/path/to/your/geoserver/home
2. geoserver-init.properties (ie edit a file after the war has been
unziped by servlet)
3. Servlet context (customize the web.xml deployment descriptor to
include a <context-param> called geoserver.home
Apparently some application servers will let you play with System
properties, or context params
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real
users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/