[FELIX-6667] Reresoliving hosts or resolving new fragments does not invalidate meta-data cache for SCR

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: scr-2.2.6
• Fix Version/s: scr-2.2.8, scr-2.2.10
• Component/s: Declarative Services (SCR)
• Assignee: Tom Watson
• Reporter: Tom Watson
• Created: 01/Nov/23 14:35
• Updated: 02/May/24 13:20
• Resolved: 02/May/24 13:20

Description

There are two cases where the component meta-data that is cached per bundle does not react to dynamic changes at runtime.

1. Fragments are installed and then the host bundle is refreshed to allow the fragments to attach. The fragments may provide their own component XML resources. In this case a bundle event is fired indicating the host bundle got UNRESOLVED. We should remove the cached meta-data for the bundle any time it gets UNRESOLVED to force it to be re-generated when the host bundle is activated again with the current set of attached fragments
2. Fragments are installed that meet the criteria to allow them to be attached dynamically to a currently resolved host. In this case we should also force the host cache to be removed so when the host is re-activated we will re-generate the meta-data with the current set of resolved fragments.

Issue Links

• links to: GitHub Pull Request #242