[
https://issues.apache.org/jira/browse/CONFIGURATION-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491785
]
Emmanuel Bourg commented on CONFIGURATION-159:
----------------------------------------------
I'm thinking about adding a flush() method to the Configuration interface
similar to the flush() method in the Preferences API :
http://java.sun.com/javase/6/docs/api/java/util/prefs/Preferences.html#flush()
The concept of making the changes persistent is not specific to the file
configurations, we need it here for CompositeConfiguration, and we'll need it
for DatabaseConfiguration to implement the caching mechanism.
> Save the changes made to a CompositeConfiguration
> -------------------------------------------------
>
> Key: CONFIGURATION-159
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-159
> Project: Commons Configuration
> Issue Type: Improvement
> Affects Versions: 1.0
> Environment: Operating System: All
> Platform: All
> Reporter: Sagar Kar
> Priority: Minor
> Fix For: 1.5
>
>
> Hi,
> I used a CompositeConfiguration object to load all my properties and xml
> files.
> I expose these configuration properties in a JMX console.
> These properties coming from many different files can be modified at runtime
> in
> memory. But I need to store these back to the original files from where they
> were picked, so that I dont loose them if the server is restarted.
> The problem that I faced is whenever a property is being modified, it gets
> moved
> from the original configuration to a BaseConfiguration object.
> What I would like is the change being made to the original configuration
> object
> as well.
> Thanks ,
> Sagar
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
