[
https://issues.apache.org/jira/browse/FELIX-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed FELIX-392.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
Fixed in Rev. 582225 by throwing an InvocationTargetException enclosing the
Throwable, which caused the failure. This results in the respective operation
to fail in the same way as if the method could be found and called but would
have thrown an exception.
Also deployed new SNAPSHOT build 20071005.121652-7 containing the fix.
> 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
> Fix For: 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.
