[CONFIGURATION-315] CombinedConfiguration fire EVENT_COMBINED_INVALIDATE even before the contained configuration is updated

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5
• Fix Version/s: 1.6
• Component/s: Events & Notifications

Environment

Any

• Assignee: Oliver Heger
• Reporter: Andy Yeung
• Created: 27/Feb/08 06:53
• Updated: 22/Aug/09 19:36
• Resolved: 02/Mar/08 21:09

Description

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.