Hi Mike, Basically this is a legacy decision as when the system was written we were in the midst of JDK4, which didn't have Environment variable support. Nowadays, we could probably update this. Would you like to file a JIRA issue and provide a patch?
Cheers, Chris On 1/15/13 10:58 AM, "Starch, Michael D (388L)" <michael.d.sta...@jpl.nasa.gov> wrote: >Hi All, > >Why does the OODT Commons code for reading environment variables run the >command line utility "env" instead of calling System.getEnvironment()? > >http://svn.apache.org/repos/asf/oodt/trunk/commons/src/main/java/org/apach >e/oodt/commons/exec/EnvUtilities.java > >We are running into transient problems in our version where environment >variables are sometimes being set to null. I am wondering if this is a >problem with the added complexity of running env over and over again >getting env variables, instead of using the built in java mechanisms for >getting this info. > >-Michael
