[FELIX-392] Better handle unexpected issues when trying to get a activation or binding method by reflection

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: scr-1.0.0
• Component/s: Declarative Services (SCR)
• Assignee: Felix Meschberger
• Reporter: Felix Meschberger
• Created: 05/Oct/07 12:10
• Updated: 30/May/08 18:15
• Resolved: 05/Oct/07 12:17

Description

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.