Hey all, I too have used a tool more than once to disable a component [1], most of the time because built in components of a system you don't have under control are doing unexpected behaviour (like throwing nullpointer exceptions / errors / ...) and we are not able to solve this unless by disabling the component (of which we don't control the source code so we can't change the configuration). You then have to get the library owners to fix it, which sometimes takes weeks / months to release a hotfix for it. What would be so bad about creating something to manage this?
[1] https://adobe-consulting-services.github.io/acs-aem-commons/features/osgi-disablers/component-disabler/index.html <https://adobe-consulting-services.github.io/acs-aem-commons/features/osgi-disablers/component-disabler/index.html> Greets, Roy > On 24 Mar 2018, at 10:36, Carsten Ziegeler <cziege...@apache.org> wrote: > > I tend to agreee, requiring a config is usually the way we solve it. > > You could also simply repackage the bundle and simply change the > component XML inside. This gives you full control. Can be easily done by > a tool. > > Regards > Carsten > > David Jencks wrote >> 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) > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org
