Emmanuel Bourg - 14/Sep/05 12:02 PM This issue has been on the todo list for quite some time. It could be quickly fixed by changing the reload() method in AbstractFileConfiguration, it may look like this : public void reload() { synchronized (reloadLock) { if (noReload == 0 && strategy.reloadingRequired()) { // save the properties Map previousProperties = new LinkedMap(store); try { clear(); load(); // notify the strategy strategy.reloadingPerformed(); } catch (Exception e) { e.printStackTrace(); // rollback the changes store = previousProperties; } } } } I'm not sure it's the best way to rollback the changes though, copying the properties seems expensive. Any idea ? Should we add a safeReload flag to enable/disable this feature ?

Emmanuel Bourg - 13/Apr/07 04:10 PM The copy of the store can be avoided by keeping a reference to the previous store and creating a new empty store before loading the file : Map previousStore = store; store = new LinkedMap(); However this will only work for the "flat" configurations like PropertiesConfiguration and INIConfiguration, the hierarchical configurations like XMLConfiguration don't use the Map in BaseConfiguration to store the properties.