[
https://issues.apache.org/jira/browse/FELIX-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger resolved FELIX-3647.
--------------------------------------
Resolution: Fixed
Fixed in Rev. 1380116 by passing a non-null MethodResult to be used if the
called method throws.
Thus null is only returned from trying to call the modified method if no such
method exists and thus the regular deactivation-activation cycle has to be used.
> Component modification must continue if modify method throws
> ------------------------------------------------------------
>
> Key: FELIX-3647
> URL: https://issues.apache.org/jira/browse/FELIX-3647
> Project: Felix
> Issue Type: Bug
> Components: Declarative Services (SCR), Specification compliance
> Affects Versions: scr-1.6.0
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.6.2
>
>
> If the modify method of a Component throws an exception (and thus fails) the
> component modification must continue as if the modify method call succeeded;
> just an error message must be logged.
> Currently, the component is deactivated and reactivated in this case thus
> being non-spec compliant
> (See Section 112.5.13, Modified Method in the Compendium R 4.3 specification)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
