You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Cameron Rochester (JIRA)" <ji...@apache.org> on 2011/08/11 07:23:27 UTC

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

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
         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

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

Posted by "Cameron Rochester (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13082928#comment-13082928 ] 

Cameron Rochester commented on FELIX-3075:
------------------------------------------

Note, 

This does not affect the release 1.8.0 - the changes made for FELIX-2989 introduced the issue.

> 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
>              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

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

Posted by "Cameron Rochester (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-3075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cameron Rochester updated FELIX-3075:
-------------------------------------

    Attachment: ProvidedService.diff

Diff to solve non-registration issue.

> 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
>              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

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

Posted by "Clement Escoffier (JIRA)" <ji...@apache.org>.
     [ 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

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

Posted by "Clement Escoffier (JIRA)" <ji...@apache.org>.
     [ 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