[
https://issues.apache.org/jira/browse/FELIX-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated FELIX-392:
------------------------------------
Fix Version/s: (was: felix-1.0.0)
scr-1.0.0
> 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 (SCR)
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: scr-1.0.0
>
>
> 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.
