Robert Munteanu created SLING-4200:
--------------------------------------
Summary: MockOsgi.activate() does not consider the default
activate method name
Key: SLING-4200
URL: https://issues.apache.org/jira/browse/SLING-4200
Project: Sling
Issue Type: Bug
Components: Testing
Affects Versions: Testing OSGi Mock 1.0.0
Reporter: Robert Munteanu
When issuing and MockOsgi.activate call, the code tries to read the OSGi
metadata and find the method declared in the SCR descriptor.
However, activate/deactivate methods don't necessarily have to use that
annotation, as the default values ensure that a method named
'activate'/'deactivate' is picked up.
The rules are actually more complicated when several methods with the matching
name exist, see the OSGi Service Platform Service Compendium, Declarative
Services specification ( checked with Version 1.2 ), entries 112.5.8 ,
112.5.15, and also 112.9.4 and the annotation is just a
But a good first step would be to account for the default method names.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
