You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2010/08/05 16:28:16 UTC

[jira] Commented: (FELIX-2523) Component must be reactivated even if modified method is declared

    [ https://issues.apache.org/jira/browse/FELIX-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895694#action_12895694 ] 

Felix Meschberger commented on FELIX-2523:
------------------------------------------

Fixed test case in Rev. 982640 for component reactivation after configuration deletion

> Component must be reactivated even if modified method is declared
> -----------------------------------------------------------------
>
>                 Key: FELIX-2523
>                 URL: https://issues.apache.org/jira/browse/FELIX-2523
>             Project: Felix
>          Issue Type: Bug
>          Components: Declarative Services (SCR)
>    Affects Versions:  scr-1.4.0
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>             Fix For:  scr-1.4.2
>
>
> According to Section 112.7.1, Modified Configuration (OSGi Compendium R4.2), a component must be deactivated if it uses a configuration which has been deleted. This happens regardless of whether a modified method is declared and available to be called or not.
> Our current implementation does not care whether a configuration is just updated or actually deleted when trying to call the modified method. This violates the spec in the case of configuration deletion.

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