[ https://issues.apache.org/jira/browse/FELIX-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on FELIX-368 started by Felix Meschberger. > Service binding odities if (un)bind methods take ServiceReferences > ------------------------------------------------------------------ > > Key: FELIX-368 > URL: https://issues.apache.org/jira/browse/FELIX-368 > Project: Felix > Issue Type: Bug > Components: Declarative Services > Reporter: Felix Meschberger > Assignee: Felix Meschberger > > 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. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.