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 2012/09/03 03:12:07 UTC
[jira] [Created] (FELIX-3647) Component modification must continue
if modify method throws
Felix Meschberger created FELIX-3647:
----------------------------------------
Summary: 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
[jira] [Closed] (FELIX-3647) Component modification must continue
if modify method throws
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger closed FELIX-3647.
------------------------------------
Close after release
> 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
[jira] [Resolved] (FELIX-3647) Component modification must continue
if modify method throws
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ 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