You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2014/11/26 23:00:13 UTC

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

    [ https://issues.apache.org/jira/browse/SLING-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14226860#comment-14226860 ] 

Stefan Seifert commented on SLING-4201:
---------------------------------------

it was not fully silent, a WARN was logged during unit tests. but you are correct, if it is declared in SCR metadata an exception should be thrown if it does not exist.

fixed in rev. 1641947 in latest snapshot

> MockOsgi.activate()/deactivate()/modified() should fail fast if method is declared but can't be found
> -----------------------------------------------------------------------------------------------------
>
>                 Key: SLING-4201
>                 URL: https://issues.apache.org/jira/browse/SLING-4201
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: Testing OSGi Mock 1.0.0
>            Reporter: Robert Munteanu
>            Assignee: Stefan Seifert
>              Labels: mocks
>             Fix For: Testing OSGi Mock 1.1.0
>
>
> 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)