DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=34441>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=34441 ------- Additional Comments From [EMAIL PROTECTED] 2005-04-18 12:17 ------- I had a look at this issue, but am yet unsure about the best way to solve it. Here are some of my thoughts: - In general setting both a reloading strategy and auto save mode can always lead to problems because there can be concurrent changes in both the Configuration object and the configuration file. Then the results cannot be predicted. - In this special case the problem lies in the call to getKeys() in the save() method of PropertiesConfiguration. So a quick (and dirty?) solution would be to access the properties in a different way, maybe by making the map with the properties in BaseConfiguration protected. - In the current implementation there is more danger potential in the collaboration of save() methods and reloading behavior, e.g. a getProperty() call might also cause a reload. So it might make sense to disable reloading as long as a save() operation is executed. This could be achieved by setting a flag (or increasing a counter) at the entrance of a save() method and resetting this flag again in a finally block. If this flag is set, the reload() method would do nothing. I don't know the affected code too well, so I might be missing something obvious. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
