felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Meschberger (JIRA)" <j...@apache.org>
Subject [jira] Closed: (FELIX-365) DependencyManager.getBindingMethod may throw NullPointerException
Date Mon, 17 Sep 2007 08:54:32 GMT

     [ https://issues.apache.org/jira/browse/FELIX-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Felix Meschberger closed FELIX-365.
-----------------------------------

    Resolution: Fixed

The bind, addingService, unbind and removedService methods now check whether a bind or unbind
method
is configured for the component before trying to call such a method.

Fixed in Rev. 576308 (also fixing FELIX-364)

> DependencyManager.getBindingMethod may throw NullPointerException
> -----------------------------------------------------------------
>
>                 Key: FELIX-365
>                 URL: https://issues.apache.org/jira/browse/FELIX-365
>             Project: Felix
>          Issue Type: Bug
>            Reporter: Felix Meschberger
>            Assignee: Felix Meschberger
>
> If a component is activated, the DependencyManager.bind method is called for each service
reference. If the reference is configured without a bind method, this method should do nothing
at all. Instead currently, it just calls the DependencyManager.invokeBindMethod which ultimately
tries to locate the bind method which is null and hence a NullPointerException is thrown.
> The DependencyManager.bind method should check whether a bind method is actually configured.
If not, the method should do nothing. Likewise, the DependencyManager.unbind method should
check whether an unbind method is actually configured.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message