I agree. I don't think normal geronimo startup should involve
copying stuff from one location to another to set up a new server
location. We could build some kind of admin server to manage setting
up/removing server "clones" but I don't think it should be part of
the base server normal startup path. If I've misunderstood what you
are proposing please complain :-)
thanks
david jencks
On Apr 25, 2007, at 11:55 AM, Jason Dillon wrote:
Just make users copy the directory and be done with it.
--jason
On Apr 25, 2007, at 4:58 AM, Anita Kulshreshtha wrote:
On a closer inspection this alternative (2) does not look so
attractive. IIUC, The classes to determine the geronimo install
directory and directory copy are available in system module.
Either we
duplicate the code in kernel or wait till later (after booting
kernel,
loading bootstrap configuration..) to fail if the instance data is
not
found.
Yet another alternative (3) is to modify the build and create a
geronimo/var and make 'var' read only.
Thanks
Anita
--- Dain Sundstrom <[EMAIL PROTECTED]> wrote:
+1
I think the platform scripts should be as thin as possible
-dain
On Apr 24, 2007, at 12:38 PM, Jason Dillon wrote:
..............................
and then just die
quickly if the directory is missing with an informative error
message to that effect.
--jason
On Apr 24, 2007, at 12:32 PM, Anita Kulshreshtha wrote:
The other option is to update MainConfigurationBootstrapper as
follows:
1. if geronimo.org.apache.geronimo.server.name system property is
not
set, set it to 'geronimo'.
2. If 'geronimo' dir does not exist, create one and copy 'var' to
it.
3. do the rest...
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
