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/12/10 00:17:13 UTC

[jira] [Closed] (SLING-4142) MockOsgi: Activate/Deactivate method does not support different signatures

     [ https://issues.apache.org/jira/browse/SLING-4142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Seifert closed SLING-4142.
---------------------------------
    Assignee:     (was: Stefan Seifert)

> MockOsgi: Activate/Deactivate method does not support different signatures
> --------------------------------------------------------------------------
>
>                 Key: SLING-4142
>                 URL: https://issues.apache.org/jira/browse/SLING-4142
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: Testing OSGi Mock 1.0.0
>            Reporter: Stefan Seifert
>              Labels: mocks
>             Fix For: Testing OSGi Mock 1.1.0
>
>
> currently for activating/deactivating osgi services in the mock environments only activate/deactivate methods with a single componentcontext object are supported.
> it should search for methods with:
> # The method takes a single argument and the type of the argument is
> org.osgi.service.component.ComponentContext.
> # The method takes a single argument and the type of the argument is org.osgi.framework.BundleContext.
> # The method takes a single argument and the type of the argument is the java.util.Map.
> # For deactivation methods only: The method takes a single argument and the type of the argument is the
> int.
> # For deactivation methods only: The method takes a single argument and the type of the argument is the
> java.lang.Integer.
> # The method takes two or more arguments and the type of each argument must be
> org.osgi.service.component.ComponentContext, org.osgi.framework.BundleContext or java.util.Map. For the deactivation method int or java.lang.Integer are allowed types as well. If multiple
> methods match this rule, this implies the method name is overloaded and SCR may choose any of the
> methods to call.
> # The method takes zero arguments.



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