[ https://issues.apache.org/jira/browse/FELIX-6667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Watson updated FELIX-6667: ------------------------------ Fix Version/s: scr-2.2.10 scr-2.2.8 > Reresoliving hosts or resolving new fragments does not invalidate meta-data > cache for SCR > ----------------------------------------------------------------------------------------- > > Key: FELIX-6667 > URL: https://issues.apache.org/jira/browse/FELIX-6667 > Project: Felix > Issue Type: Bug > Components: Declarative Services (SCR) > Affects Versions: scr-2.2.6 > Reporter: Tom Watson > Assignee: Tom Watson > Priority: Major > Fix For: scr-2.2.8, scr-2.2.10 > > > There are two cases where the component meta-data that is cached per bundle > does not react to dynamic changes at runtime. > # 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 > # 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. -- This message was sent by Atlassian Jira (v8.20.10#820010)