The other thought with preserving the base /var files in a jar/zip - it allows an admin/root user to install the base server files and then allow users to create their own instances by extracting the JEE5 or Minimal var jar/zip bundle (or a custom bundle that their IT guys create per dept or project.)
Either way works for me, as we can always create a Java or JMX wrapper for creating/deleting instances in a future release.
-Donald Jason Dillon wrote:
Actually, what is in var that needs to be so pristine? Stuff put into var dirs are generally very dynamic and heavily state driven... not sure why that would need to be kept pristine across instances... sans the log4j configuration files, which really belong in an etc/ or conf/ and no in var/...--jason On Apr 25, 2007, at 7:25 PM, Donald Woods wrote:What about creating a jar/zip of the var directory when the assembly is created, so you always have a pristine copy and could easily use a script to unjar/unzip it into a new directory via the user's JVM?-Donald Anita Kulshreshtha wrote:--- David Jencks <[EMAIL PROTECTED]> wrote: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.This is needed because we need to keep a pristine copy of 'var' directory to create additional instances of geronimo. A user should be able to use the installed image _any_ time to create additional instances. In other words we need two copies of 'var' directory, one to create additional instance and one to start the 'base server'. We could either create var and geronimo/var at build time or copy 'var' to geronimo/var when the image is used to start geronimo very _first_ time. Thanks Anita We could build some kind of admin server to manage settingup/removing server "clones" but I don't think it should be part of the base server normal startup path. If I've misunderstood what youare proposing please complain :-) thanks david jencks On Apr 25, 2007, at 11:55 AM, Jason Dillon wrote:--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 installdirectory 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 isnot 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 diequickly 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 MainConfigurationBootstrapperasfollows: 1. if geronimo.org.apache.geronimo.server.name system propertyisnotset, set it to 'geronimo'. 2. If 'geronimo' dir does not exist, create one and copy 'var'toit.3. do the rest...__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com__________________________________________________ Do You Yahoo!?Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
smime.p7s
Description: S/MIME Cryptographic Signature
