Could you describe the behavior you want in a little more detail? Is there a global switch to turn this on, or per bundle, or per component? What happens when you upgrade a bundle to a new version? How do you clear the slate and start over with no persisted enablement info? How do you get a report of the enablement overrides?
So far I’m not thrilled with the idea of adding a persistence mechanism to scr, but I haven’t run into the scenarios you mention. I’d think making the components configuration required and dealing with config admin would be a simpler approach. David Jencks Sent from my iPhone > On Mar 23, 2018, at 7:40 AM, Raymond Auge <raymond.a...@liferay.com> wrote: > > Hello All, > > I know this topic has come up many different times. > > I'd like to request support for persistent component state (i.e. > persistently enable/disable) components. > > I've created an issue for it > https://issues.apache.org/jira/browse/FELIX-5817 > > I will also try in the next while to implement it to see what this would > look like. > > Sincerely, > -- > *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> > (@rotty3000) > Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> > (@Liferay) > Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
