[
https://issues.apache.org/jira/browse/FELIX-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-2523.
--------------------------------------
Resolution: Fixed
In Rev. 982606 checking for configuration deletion before trying to call the
modified method. Instead of calling the modified method (if declared), the
component is reactivated.
> 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.
