[ 
https://issues.apache.org/jira/browse/CONFIGURATION-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12583826#action_12583826
 ] 

Oliver Heger commented on CONFIGURATION-319:
--------------------------------------------

You are right, CompositeConfiguration does not correctly handle change 
listeners and change events.

Could you try CombinedConfiguration instead? This class should provide the 
functionality you need, and it also has some other advantages over 
CompositeConfiguration - especially it is a truly hierarchical configuration.

CompositeConfiguration is a bit, well, old-fashioned. In the long run it should 
be replaced by CombinedConfiguration. So I wonder if it makes sense to address 
this issue when there is a working alternative.

> Reload(addConfigurationListern) not works for CompositeConfiguration
> --------------------------------------------------------------------
>
>                 Key: CONFIGURATION-319
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-319
>             Project: Commons Configuration
>          Issue Type: Bug
>    Affects Versions: 1.5
>         Environment: Linux  2.6.9-34.ELsmp #1 SMP Fri Feb 24 16:54:53 EST 
> 2006 i686 i686 i386 GNU/Linux
>            Reporter: Sandeep Kumar
>
>  I created 2 XMLConfiguration and added this to CompositeConfiguration using 
> addConfiguration. Now I addConfigurationListern at CompositeConfiguration 
> level. Currently CompositeConfiguration.addConfigurationListern is not 
> overriden and addConfigurationListern never get registeded to any of actual 
> configuration. The solution could be override the 
> CompositeConfiguration.addConfigurationListern which iterate though 
> configList(a private member of CompositeConfiguration class) and registed 
> listern to all the configuration. In current code this is broken funtionality 
> and callback ConfigurationListener.configurationChanged never fired.
>   while reproducing this problem I am calling 
> CompositeConfiguration.getProperty() every minute for reloading from another 
> thread.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to