[
https://issues.apache.org/jira/browse/FELIX-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533038
]
Felix Meschberger commented on FELIX-392:
-----------------------------------------
I just want to add an update on the LinkageError issue causing the problems: In
fact the class causing the error is not exported yet, the it is declared as the
return value of an interface which is exported. This of course is incosistent
and cannot be handled correctly. In fact it was en error, because the return
value should have been declared with an exported interface implemented by the
wrongfully declared class.
> 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.
