[TAMAYA-232] Implementation of ConfigurationChange is not consistent

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.3-incubating
• Fix Version/s: 0.3-incubating
• Component/s: Extensions
• Assignee: Oliver B. Fischer
• Reporter: Oliver B. Fischer
• Created: 29/Jan/17 21:44
• Updated: 18/Sep/17 19:35
• Resolved: 06/Apr/17 19:42

Description

The implementation of ConfigurationChange is not consistent. While the methods getAddedSize(), getRemovedSize() and getUpdatedSize() ignore properties starting with the prefix _ ignore, does isEmpty() simply counts the number changes without the same filtering mechnism.

This leeds the to unneeded fired events, as the method isEmpty() is used by checkConfigurationUpdate() of DefaultConfigChangeObserver returns always false.

At the moment every ConfigurationChange contains two properties starting with _ which have been added to FrozenConfiguration during its construction.

Issue Links

• is related to: TAMAYA-243 Change event does not contain the new value for a key after changing its value