Mailing-List: contact geronimo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: geronimo-dev@incubator.apache.org
Message-ID: <099601c35dd8$7b897170$2d01a8c0@chariotsolutions.com>
From: "Erin Mulder" <meara@alumni.princeton.edu>
To: <geronimo-dev@incubator.apache.org>
References: <DB47CC74-C9C5-11D7-8489-0003934D3EA4@ioshq.com>
 <3F33E53A.6070004@kebernet.net>
Subject: Re: One True Way (TM) of handling configuration files
Date: Fri, 8 Aug 2003 14:11:25 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Alex Blewitt wrote:
> >  From an administrator's PoV, it would be nicer if all configuration
> > could be done via an admin console, and for the repository to be stored
> > in a not-necessarily-human-readable form which was updated as the config
> > was changed via the admin console (e.g. Web app)

Robert Responded
> While this may be a matter of some personal preference, I tend to like
> config files over an admin cosole/webapp. Being able to
> administer/maintain via a command line is imporant to me.

I am all in favor of a good admin console, but everything should still be
accessible through XML config files and the command line.

One of the most common complaints about Websphere (4.x at least) is the way
it obfuscates all the configuration files.  GUI tools are great for
administration of shared servers, but not for development.   I want a good
record of any configuration changes I make and an easy, legible way to share
them with other developers (see the "User Friendliness" thread).

Erin