Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Fri, 21 Oct 2011 13:24:32 +0000 (UTC)
From: "Emmanuel Bourg (Updated) (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: 
 <2141390039.841.1319203472247.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CONFIGURATION-159) Save the changes made to a
 Composite/CombinedConfiguration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CONFIGURATION-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bourg updated CONFIGURATION-159:
-----------------------------------------

    Summary: Save the changes made to a Composite/CombinedConfiguration  (was: Save the changes made to a CompositeConfiguration)
    
> Save the changes made to a Composite/CombinedConfiguration
> ----------------------------------------------------------
>
>                 Key: CONFIGURATION-159
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-159
>             Project: Commons Configuration
>          Issue Type: Improvement
>    Affects Versions: 1.0
>            Reporter: Sagar Kar
>            Priority: Minor
>             Fix For: 2.0
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira