[
https://issues.apache.org/jira/browse/SLING-7550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sufyan Haroon updated SLING-7550:
---------------------------------
Description:
When invoking BundleContext
[api|https://osgi.org/javadoc/r4v43/core/org/osgi/framework/BundleContext.html#getServiceReferences(java.lang.String,
java.lang.String)], when the class parameter is specified as null and filter
param is non-null, it is expected to return reference of all services which
satisfy the filter regardless of their class.
When the same api is invoked in MockBundleContext, it does not returns any
service references when class param is null and filter param is non-null.
MockBundleContextshould behave is a way which is similar to original
implementation
> MockBundleContext does not get service references when class is null and
> filter is non-null
> -------------------------------------------------------------------------------------------
>
> Key: SLING-7550
> URL: https://issues.apache.org/jira/browse/SLING-7550
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing OSGi Mock 2.3.6
> Reporter: Sufyan Haroon
> Priority: Major
> Fix For: Testing OSGi Mock 2.3.8
>
>
> When invoking BundleContext
> [api|https://osgi.org/javadoc/r4v43/core/org/osgi/framework/BundleContext.html#getServiceReferences(java.lang.String,
> java.lang.String)], when the class parameter is specified as null and filter
> param is non-null, it is expected to return reference of all services which
> satisfy the filter regardless of their class.
> When the same api is invoked in MockBundleContext, it does not returns any
> service references when class param is null and filter param is non-null.
> MockBundleContextshould behave is a way which is similar to original
> implementation
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
