You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2014/11/26 17:22:12 UTC

[jira] [Created] (SLING-4201) MockOsgi.activate()/deactivate() should fail fast if method is declared can't be found

Robert Munteanu created SLING-4201:
--------------------------------------

             Summary: MockOsgi.activate()/deactivate() should fail fast if method is declared can't be found
                 Key: SLING-4201
                 URL: https://issues.apache.org/jira/browse/SLING-4201
             Project: Sling
          Issue Type: Bug
            Reporter: Robert Munteanu


When activating/deactivating a method MockOsgi should throw an exception if the activate/deactivate attribute is specified and no suitable method
is located ( to paraphrase the OSGi compendium spec, section 112.5.8 ) . Otherwise we just get a silent failure to activate/deactivate the component




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)