kwin edited a comment on pull request #13: URL: https://github.com/apache/sling-org-apache-sling-testing-osgi-mock/pull/13#issuecomment-974385346
The failing use case is: 1. DS component registered automatically for service A 2. DS component manually registered as service B (either in activate() or some other explicit method) 3. DS component unregisters service B in its deactivate method 3. DS component deactivated via MockBundleContext.shutdown() a) Service B -> deactivate called -> calls BundleContext.unregisterService() . b) Service A -> deactivate called -> calls BundleContext.unregisterService() again. I will add some test which is failing with calling deactivate() multiple times on the same object. Regarding: > what do you mean with DS component registry - calling deactivate only on DS components? Simple OSGi services can be any type of Mojo. (De-)activate methods are only defined and ever called for DS components according to the OSGi specs! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
