felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clement Escoffier (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FELIX-3075) Change to ServiceController status in current trunk does not re-register service
Date Fri, 12 Aug 2011 10:20:27 GMT

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

Clement Escoffier resolved FELIX-3075.
--------------------------------------

       Resolution: Fixed
    Fix Version/s: ipojo-core-1.8.2

Hi,

I've applied the patch in the trunk. Thanks !

> 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
>             Fix For: ipojo-core-1.8.2
>
>         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

        

Mime
View raw message