You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@felix.apache.org by "Clement Escoffier (JIRA)" <ji...@apache.org> on 2011/08/11 10:50:27 UTC

[jira] [Assigned] (FELIX-3075) Change to ServiceController status in current trunk does not re-register service

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

Clement Escoffier reassigned FELIX-3075:
----------------------------------------

    Assignee: Clement Escoffier

> Change to ServiceController status in current trunk does not re-register service
> --------------------------------------------------------------------------------
>
>                 Key: FELIX-3075
>                 URL: https://issues.apache.org/jira/browse/FELIX-3075
>             Project: Felix
>          Issue Type: Bug
>          Components: iPOJO
>    Affects Versions: ipojo-core-1.8.2
>            Reporter: Cameron Rochester
>            Assignee: Clement Escoffier
>              Labels: ipojo
>         Attachments: ProvidedService.diff
>
>
> The setValue method in ServiceController is ignoring changes to controller fields. If the value is set to true, and there is already a registration, then the method will not do anything. This occurs where you have a component that provides multiple interfaces but one is disabled on startup. When the serviceController for the disabled interface is changed to true the other, non-registered, interface is not registerd. I will attempt to attach a patch to ProvidedService that resolved the problem for me.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira