[CONFIGURATION-223] PropertiesConfigurationLayout broke the autoSave behaviour of PropertiesConfiguration

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Fix Version/s: 1.3

Environment

1.3RC1

• Assignee: Oliver Heger
• Reporter: Gabriele Garuglieri
• Created: 28/Aug/06 12:45
• Updated: 22/Aug/09 19:36
• Resolved: 30/Aug/06 19:21

Description

When using PropertiesConfiguration with autoSave "true" the PropertiesConfigurationLayout causes invalid properties files to be saved.

When using addProperty("key", "value"); where key does not exist yet in the configuration the EVENT_ADD_PROPERTY event that updates the PropertiesConfigurationLayout with the new "key" is issued only after the possiblySave() method is invoked so the new property will not be saved.

When using setProperty("key", "value"); where key does not exist yet in the configuration the EVENT_SET_PROPERTY event that updates the PropertiesConfigurationLayout with the new "key" is issued only after the possiblySave() method is invoked so the new property will not be saved.

The way it is implemented now makes content of the saved file depending on PropertiesConfigurationLayout content that depends on an event that will be issued only after the file was properly updated. This creates a circular dependency that cannot work.