+1 to Matt's suggestion. I know that there are already users working on
unstable builds of 1.1. While I think that they understand 1.1 isn't
final yet ... we've already forced them to change a good many things.
I think it would be nice to avoid any more for 1.1 so I'd vote for
option #1.
Joe
Matt Hogstrom wrote:
I'm fine for leaving the code in 1.1 to play with but I'm -1 in
promoting it in 1.1. This should be a 1.2 item. One of the reasons we
end up making disruptive changes later in the release is we don't have
time to think this through and we'll be unhappy with the answer and end
up tweaking it next time.
That said, for 1.2 this is really needed as clustering will probably
take shape. I'd prefer to start the discussion now and finish it in
1.2. Here's my 2c.
geronimo/servers/default
geronimo/servers/foo
geronimo/servers/server1
geronimo/servers/server2
A major grouping off of Geronimo makes sense so we can group servers
together. It would make sense to me to leave geronimo/var as the
legacy, single server and the above as the clustered convention.
Aaron Mulder wrote:
All,
David Jencks just backported a feature that lets you create multiple
server configurations inside a single Geronimo installation. This
affects the contents of the var/ directory, if I understand it right.
So essentially, you could create a structure like this:
geronimo/var/... (default configuration)
geronimo/server1/var/... ("server1" configuration)
geronimo/another/var/... ("another" configuration)
In other words, you can create subdirectories with their own copies of
var/* and then tell Geronimo during startup to read from foo/var/*
instead of var/* using a command-line parameter.
I'd like to propose one change to this, and that is, that we eliminate
the "var" directory and set it up one of these two ways -- the
difference being whether the default server configuration is named
something like "default" or named "var":
Option 1: default configuration named "var":
geronimo/var/... (default configuration)
geronimo/server1/... ("server1" configuration)
geronimo/another/... ("another" configuration)
Option 2: default configuration named e.g. "default":
geronimo/default/... (default configuration)
geronimo/server1/... ("server1" configuration)
geronimo/another/... ("another" configuration)
It seems somewhat more usable to me if, for example, the log directory
is immediately underneath the server configuration directory. For
anyone who's not real UNIX-oriented, I think it will be much nicer to
look in the configuration directory and see config/ log/ security/ etc
instead of just seeing "var".
Any thoughts on this?
Thanks,
Aaron
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
