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/01/26 13:38:34 UTC
[jira] Work started: (FELIX-2006) If an Error is thrown
instantiated a component, the component remains in the Activating state and
cannot be managed any longer
[ https://issues.apache.org/jira/browse/FELIX-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on FELIX-2006 started by Felix Meschberger.
> If an Error is thrown instantiated a component, the component remains in the Activating state and cannot be managed any longer
> ------------------------------------------------------------------------------------------------------------------------------
>
> Key: FELIX-2006
> URL: https://issues.apache.org/jira/browse/FELIX-2006
> 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
>
>
> If an Error (e.g. ClassDefNotFoundError) is thrown in the ImmediateComponentManager.createImplementationObject method, this error is propagated through the complete call stack and caught outside of the ComponentManager thus leaving the ComponentManager in an uncontrollable state, namely "Activating".
> The createImplementationObject method should catch Throwable and just log and return null if the implementation object cannot be instantiated due to an Error being thrown.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.