[FELIX-368] Service binding odities if (un)bind methods take ServiceReferences

• Type: Bug
• 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: 17/Sep/07 09:34
• Updated: 30/May/08 18:15
• Resolved: 17/Sep/07 11:02

Description

When a service is bound by calling the configured bind method, the service may be given as the service itself or as its ServiceReference. The intent is to be able to first inspect the reference properties before actually getting the service or to delay activation of a service
component until the service is really needed.

Currently, the service object is always accessed before calling the bind method regardless of whether the service object is really needed or not. Likewise for the unbind method, which always requires the service object regardless of whether it is used to call the unbind method.

In addition, the handling of the arguments of the bind and unbind methods using the m_bindUsesServiceReference field is wrong if the on of the methods takes the service instance while the other takes a ServiceReference.