[
https://issues.apache.org/jira/browse/SLING-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-4163.
-----------------------------------
Resolution: Fixed
Completed: At revision: 1639692
> OSGi Mock: Reference bind/unbind method picking order
> -----------------------------------------------------
>
> Key: SLING-4163
> URL: https://issues.apache.org/jira/browse/SLING-4163
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing OSGi Mock 1.0.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Minor
> Fix For: Testing OSGi Mock 1.1.0
>
>
> ensure bind/unbind method selection complies to osgi 4.3 standard:
> # The method takes a single argument and the type of the argument is
> org.osgi.framework.ServiceReference.
> # The method takes a single argument and the type of the argument is the type
> specified by the reference’s interface attribute.
> # The method takes a single argument and the type of the argument is
> assignable from the type specified by the reference’s interface attribute. 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 two argument and the type of the first argument is the
> type specified by the reference’s interface attribute and the type of the
> second argument is java.util.Map.
> # The method takes two argument and the type of the first argument is
> assignable from the type specified by the reference’s interface attribute and
> the type of the second argument is java.util.Map. If multiple methods match
> this rule, this implies the method name is overloaded and SCR may choose any
> of the methods to call.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
