[
https://issues.apache.org/jira/browse/CONFIGURATION-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oliver Heger resolved CONFIGURATION-315.
----------------------------------------
Resolution: Fixed
You are right: sending two events per change is an inconsistent behavior.
I have applied a fix. The isBeforeUpdate() property of the change event is now
taken into account.
Thanks.
> CombinedConfiguration fire EVENT_COMBINED_INVALIDATE even before the
> contained configuration is updated
> -------------------------------------------------------------------------------------------------------
>
> Key: CONFIGURATION-315
> URL: https://issues.apache.org/jira/browse/CONFIGURATION-315
> Project: Commons Configuration
> Issue Type: Bug
> Components: Events & Notifications
> Affects Versions: 1.5
> Environment: Any
> Reporter: Andy Yeung
> Assignee: Oliver Heger
> Fix For: 1.6
>
>
> CombinedConfiguration.configurationChanged doesn't check the
> !event.isBeforeUpdate() and trigger the invalidate call. The invalidate call
> fire the EVENT_COMBINED_INVALIDATE. so now when a contained config is
> changed, EVENT_COMBINED_INVALIDATE is fired twice by the
> CombinedConfiguration. However it should only fire it after the contained
> FileConfiguration is updated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
