Re: [Wrapper-user] Re: Defining enviroment variable on the command line.

[Leif M. <le...@ta...>]

Mikkel, Rich,
    Ok, The CVS version of the Wrapper will now update all environment
variables set in the registry immediately after the Wrapper is started as
an NT Service.   I thought about this a lot and decided to make this the
default and only behavior.  The problem is that there is not any clean way
to provide a property in the conf file to control this as the decision 
whether
or not to use the registry needs to be decided before the config file is
loaded.
    I couldn't think of any reason why a user would not want to have this
functionality while running as a service anyway, so as it is currently
implemented.  Values are always read from the registry when the
Wrapper is run as a service.  Can anyone think of a case where this
could cause problems.
    When the Wrapper is run in console, service install or service remove
modes environment variables are read from the environment as was done
in previous versions.  This is necessary because the variables could be
changed from their defaults by the script used to launch the wrapper.

    Currently, there are no API or configuration changes related to this 
feature.
The only non-code change is a mention of the functionality in the docs.

Cheers,
Leif