Hi,
is it possible to disable a component inside OSGI via an xml file similiar to the OSGIconfig. I want to disable com.adobe.granite.comments.internal.CommentReplicationContentFilterFactory.
Thanks
Chris
Solved! Go to Solution.
Views
Replies
Total Likes
Hi Chris,
In short no - there's no *universal* configuration-based way to stop a component. As Davide notes, some components allow you to effectively disable them using configuration, but for components which do not have such configuration, you need to stop the component manually via the web console or through code (using the ScrService).
Justin
Views
Replies
Total Likes
Hi Chris,
In short no - there's no *universal* configuration-based way to stop a component. As Davide notes, some components allow you to effectively disable them using configuration, but for components which do not have such configuration, you need to stop the component manually via the web console or through code (using the ScrService).
Justin
Views
Replies
Total Likes
Can you please provide more details on what you want to do? It sounds like you want to dynamically disable an active OSGi bundle using XML or an API.
Views
Replies
Total Likes
You know how you can create a xml file eg
com.day.cq.rewriter.linkchecker.impl.LinkCheckerImpl.xml
and you can then place this inside your package and when this package is installed inside osgi the configurations are all set. Is there a similar method to disable the CommentReplicationContentFilterFactory component.
Chris
Views
Replies
Total Likes
That depends if the implementation of the service within a bundle allows you to disable it or not.
You could potentially stop via the felix console either the bundle or the OSGi component but I don't know what it could be the CQ behavior if you disable the CommentsReplication.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies