Passing system properties on Windows vs Unix

Carel Paradis carelparadis-dev at videotron.ca
Sun Jan 8 02:43:26 EST 2006


Hi,

I have modified the Unix scripts to ensure all DPML's applications work 
properly on this platform. Now, 4 environment variables can be provided by 
the end-user:

DEPOT_SECURITY_POLICY, DEPOT_JVM_OPTS, DEPOT_CLASSPATH and DEPOT_ARGS

The following rules are applied:

If DEPOT_SECURITY_POLICY is not already set before calling depot, then the 
default policy is taken ($DPML_SYSTEM/bin/security.policy)

If DEPOT_JVM_OPTS is already set before calling depot, then these options 
are added at the end of the standard options 
(like -Djava.system.class.loader=net.dpml.transit.SystemClassLoader). If it 
is set before calling transit, build, metro or station, then these options 
are added after the options for these applications (these options are 
themselves added after the standard options). Like this, an end-user can 
specify that the server hotspot JVM must be used without modifying the 
default scripts. It can also specify some system properties specific for its 
application.

If DEPOT_CLASSPATH is already set before calling depot, then it value is 
added at the end of the standard classpath 
($DPML_SYSTEM/lib/dpml-depot-console.jar:$DPML_SYSTEM/lib/dpml-transit-main.jar)

If DEPOT_ARGS is already set before calling depot, then it value is passed 
as application arguments before others arguments passed on the command line.

Cheers,

Carel

----- Original Message ----- 
From: "Stephen McConnell" <mcconnell at dpml.net>
To: "'DPML Development'" <dev-dpml at lists.ibiblio.org>
Sent: Saturday, January 07, 2006 10:24
Subject: RE: Passing system properties on Windows vs Unix


>
>
>> -----Original Message-----
>> From: Carel Paradis
>
>> Currently (rev 865), the system property
>> -Ddpml.depot.application is passed directly to the JVM on
>> Windows while on Unix it is passed as an application
>> argument. In order to ensure to have exactly the same
>> behavior on Unix than on Windows, I think we should pass this
>> property (and all others) to the JVM like we do for the
>> system property -Ddpml.transit.include.tools in the build
>> script. This means that only arguments specified by the user
>> on the command line will be passed as application arguments.
>>
>> What do you think?
>
> Thinking the same thing.
> Move any system property declarations in the transit, metro, station and
> build scripts into respective DEPOT_JVM_OPTS declarations should bring us 
> to
> the desired result.
> /Steve.
>
> _______________________________________________
> dev-dpml mailing list
> dev-dpml at lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/dev-dpml 




More information about the dev-dpml mailing list