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 2007/10/05 14:10:50 UTC
[jira] Work started: (FELIX-392) Better handle unexpected issues
when trying to get a activation or binding method by reflection
[ https://issues.apache.org/jira/browse/FELIX-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on FELIX-392 started by Felix Meschberger.
> Better handle unexpected issues when trying to get a activation or binding method by reflection
> -----------------------------------------------------------------------------------------------
>
> Key: FELIX-392
> URL: https://issues.apache.org/jira/browse/FELIX-392
> Project: Felix
> Issue Type: Improvement
> Components: Declarative Services
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
>
> Sometimes it may happen, that trying to get an activation (activate, deactive) or binding (bind, unbind) method throws an unexpected Throwable. For example in one use case, when updating a bundle (before refreshing packages), trying to get a bind method of one the new components throws a LinkageError which is just logged but may leave the component in an undefined half-started state.
> The AbstractComponentManager.getMethod method should catch any throwables and encapsulate them such that this situation may be handled properly.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.