You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Pierre De Rop (JIRA)" <ji...@apache.org> on 2016/06/01 15:38:59 UTC
[jira] [Created] (FELIX-5273) Wrong log when a callback is not
found from component instance(s)
Pierre De Rop created FELIX-5273:
------------------------------------
Summary: Wrong log when a callback is not found from component instance(s)
Key: FELIX-5273
URL: https://issues.apache.org/jira/browse/FELIX-5273
Project: Felix
Issue Type: Bug
Components: Dependency Manager
Affects Versions: org.apache.felix.dependencymanager-r1
Reporter: Pierre De Rop
Assignee: Pierre De Rop
Priority: Trivial
Fix For: org.apache.felix.dependencymanager-r9
When a component dependency callback is not found from the component instance(s), then sometimes (when a specific callback instance is used), the log is wrong and does not display the actual component instance(s).
For example, assume you have the following Activator:
{code}
class CallbackInstance {
void setLog(LogService log) {}
}
CallbackInstance cbInstance = new CallbackInstance();
dm.add(createComponent()
.setImplementation(Hello.class)
.add(createServiceDependency()
.setService(LogService.class).setCallbacks(cbInstance, "setLoggggg", null, null));
}
{code}
The the following error is logged:
{code}
ERROR: [main] "setLoggggg" callback not found on component instances [test.dm.Hello@7b69c6ba]
{code}
but the log is wrong, it should log the CallbackInstance class, like this:
{code}
ERROR: [main] "setLoggggg" callback not found on component instances [test.dm.CallbackInstance@7b69c6bd]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)