felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre De Rop (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-5337) Filter-based dependencies working differently for annotations
Date Sat, 12 Nov 2016 23:41:58 GMT

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

Pierre De Rop resolved FELIX-5337.
    Resolution: Fixed

added test: org.apache.felix.dependencymanager.runtime.itest/src/org/apache/felix/dm/runtime/itest/components/FELIX5337_MatchAllServicesWithFilter.java

I think this issue is resolved.

> Filter-based dependencies working differently for annotations
> -------------------------------------------------------------
>                 Key: FELIX-5337
>                 URL: https://issues.apache.org/jira/browse/FELIX-5337
>             Project: Felix
>          Issue Type: Bug
>    Affects Versions: dependencymanager-4.3.0
>            Reporter: J.W. Janssen
>            Assignee: Pierre De Rop
> I've got a "catch all" service dependency that simply wants to see *all* services being
registered. In the activator based implementation I simply express my dependency as {{createServiceDependency().setService("(objectClass=*)").setRequired(false).setCallbacks("addService",
"removeService")}} and I get all services I'm interested in (I mean: each and every registered
> However, if I rewrite my code to use annotations using {{@ServiceDependency(filter="(objectClass=*)",
required = false, removed = ...)}}, I suddenly do not see all services I expect: only services
that seem to be compatible with the class-space of the bundle my code lives in.

This message was sent by Atlassian JIRA

View raw message