[SLING-2523] Improve the JCR Installer

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: JCR Installer 3.1.4
• Component/s: Installer
• Assignee: Unassigned
• Reporter: Carsten Ziegeler
• Created: 27/Jun/12 07:01
• Updated: 07/Oct/16 07:52
• Resolved: 07/Oct/16 07:52

Description

The current implementation has some drawbacks:

• it registers several observation listeners
• to handle deletes it has to register even more listeners
• observation events are just used as markers and there is a polling thread running continously to check for changed markers and then rescan a sub tree in the repository
• changes are not reported to the OSGi installer in one method call

I think we can simplify and improve the implementation by

• just registering a single observation listener for root and then do simple path matching operations
• use the observation events to detect what has changed
• report the changes in a single method call

In addition it would be nice if the jcr installer waits befire reporting changes from an observation event and looks if there is not another observation event coming in "right after". This could improve situations where changes are not done by a single save but by a serious of saves