felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (FELIX-364) 0..1 dynamic service reference does not bind properly.
Date Mon, 17 Sep 2007 08:58:32 GMT

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

Felix Meschberger resolved FELIX-364.
-------------------------------------

    Resolution: Fixed

I have (once again) refactored the DependencyManager class:

> Only the services to which the dependency manager is actually bound is kept in an internal
map
> The number of available services is set initially from the number of already available
services and then
   updated as part of the ServiceListener.serviceChanged handling
> Access to the service instances is centralized and thus guarantees that service lookup
and service binding
   allways use the same references and that bound services are ungot when the dependency manager
is
   closed.

Could you please confirm, that this fix solves your issues. I will deploy a new snapshot after
getting your confirmation. Thanks.

> 0..1 dynamic service reference does not bind properly.
> ------------------------------------------------------
>
>                 Key: FELIX-364
>                 URL: https://issues.apache.org/jira/browse/FELIX-364
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services
>    Affects Versions: 0.8.0
>         Environment: Java 1.6
>            Reporter: I-Ann Chen
>            Assignee: Felix Meschberger
>         Attachments: patch.txt
>
>
> There are 2 parts to the issue. Both are with a component with a reference to a service
where cardinality=0..1 and policy=dynamic.
> 1. If the bundle providing the service is stopped (without another bundle providing the
same service) and restarted, the service is not re-bound to the component.
> 2. If the service is started after the component referencing it, then the service is
never bound to the component.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message