geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Sisson <>
Subject files in var/config directory
Date Sun, 04 Dec 2005 06:57:08 GMT
On the user list Erin suggested (see mail below) that some of the files 
in the var/config directory be renamed.

* Does renaming the files make less sense now that users can instruct 
Geronimo to use a specific config file (instead of the default 
config.xml file) by setting the org.apache.geronimo.config.file system 

* Erin's suggestion of the README file is worthwhile.  I suggest we call 
the README file README.txt (to simplify fixcrlf processing at packaging 
time and to make it easier for windows users to view).

* In the long term I think we should also have README.txt files in other 
major Geronimo directories so administrators can quickly familiarise 
themselves with the purpose of directories (without having to find and 
read through a  manual).  The README is not a replacement for a manual 
and can contain URLs for the full documentation.

Comments?  I'll raise JIRA(s) if we have agreement.

-------- Original Message --------
Subject: 	Re: config.xml and config.tomcat.xml
Date: 	Tue, 22 Nov 2005 17:15:49 -0500
From: 	Erin Mulder <>
References: 	<> 

Kevan Miller wrote:
> Lin,
> They represent different possible web container configurations. In a
> fresh M5 archive download (i.e. zip/tar.gz, not the installer), you
> should find 4 xml files in var/config:
> config.xml -- this is the config file which will be used when starting
> the server
> config.both.xml -- sample config settings for both jetty and tomcat
> config.tomcat.xml -- sample config settings for tomcat only
> config.jetty.xml -- sample config settings for jetty only
> For example, to switch to a jetty-only configuration, copy
> 'config.jetty.xml' to 'config.xml', and start your server.

It might be nice to rename these slightly to make that more obvious.

For example, something like:

  README (describing how this works and what to do)


View raw message