You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Oliver Heger (JIRA)" <ji...@apache.org> on 2007/01/27 19:38:49 UTC
[jira] Updated: (CONFIGURATION-223) PropertiesConfigurationLayout
broke the autoSave behaviour of PropertiesConfiguration
[ https://issues.apache.org/jira/browse/CONFIGURATION-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oliver Heger updated CONFIGURATION-223:
---------------------------------------
Fix Version/s: (was: Nightly Builds)
1.3
> PropertiesConfigurationLayout broke the autoSave behaviour of PropertiesConfiguration
> -------------------------------------------------------------------------------------
>
> Key: CONFIGURATION-223
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-223
> Project: Commons Configuration
> Issue Type: Bug
> Environment: 1.3RC1
> Reporter: Gabriele Garuglieri
> Assigned To: Oliver Heger
> Priority: Critical
> Fix For: 1.3
>
> Attachments: 223-test.patch
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org