------- Additional Comments From [hidden email] 2005-05-07 17:41 -------
The following seems to happen:
PropertiesConfiguration.load() loads the specified properties file line by line
and calls addProperty() for each detected property. In
AbstractFileConfiguration.addProperty() the new property value is stored and
then possiblySave() is called. If the auto save flag is set, this method will
trigger the save() method, which in turn will immediately overwrite the current
As a solution I suggest to store the old value of the auto save flag at the
beginning of PropertiesConfiguration.load() and set it always to false. At the
end of the method (in a finally block) the flag's old value can be reset.
autoSave really should not be enabled during execution of a load method. So it
might be better to implement such a mechanism already in
AbstractFileConfiguration (but where?). Any thoughts or comments?