>>>>> Wes Nakamura writes:
Wes> Hi,
Wes> I believe this is a bug that was introduced somewhere between
Wes> 1.1.5 and 1.1.7, but I'm not sure what the behavior really
Wes> should be. I'm not sure if it's linux-specific, but I don't
Wes> currently have another machine to test on. Basically it
Wes> looks like some system properties are being ignored after
Wes> they're changed.
Wes> I want to change the file.encoding system property within a program
Wes> instead of setting it with -Dfile.encoding= on invocation, so that the
Wes> default encoding for various classes can be changed dynamically and
Wes> constructors don't need a string encoding parameter.
[...]
Wes> I'm having a hard time finding documentation on this sort of
Wes> stuff, but I assume that the 1.1.5 behavior is correct.
No bug, the 1.1.7 behavior is correct too! There is no guarantee that
changing properties at runtime has an effect. Usually properties get
evaluated once at startup. If you change the value of a property, it
may or may not be re-evaluated.
Juergen
--
Juergen Kreileder, Universitaet Dortmund, Lehrstuhl Informatik V
Baroper Strasse 301, D-44221 Dortmund, Germany
Phone: ++49 231/755-5806, Fax: ++49 231/755-5802
