[
https://issues.apache.org/jira/browse/FELIX-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15656773#comment-15656773
]
Dobias van Buuren commented on FELIX-5403:
------------------------------------------
Thanks. The effect I see is that DM is trying to inject services of a whole
different type... see the stacktrace below
{code}
java.lang.IllegalArgumentException: argument type mismatch
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at
org.apache.felix.dm.impl.InvocationUtil.invokeMethod(InvocationUtil.java:131)
at
org.apache.felix.dm.impl.InvocationUtil.invokeCallbackMethod(InvocationUtil.java:86)
at
org.apache.felix.dm.impl.ComponentImpl.invokeCallbackMethod(ComponentImpl.java:531)
at
org.apache.felix.dm.impl.ComponentImpl.invokeCallbackMethod(ComponentImpl.java:523)
at
org.apache.felix.dm.impl.ServiceDependencyImpl.invoke(ServiceDependencyImpl.java:471)
at
org.apache.felix.dm.impl.ServiceDependencyImpl.invokeCallback(ServiceDependencyImpl.java:277)
at
org.apache.felix.dm.impl.ComponentImpl.invokeCallbackSafe(ComponentImpl.java:1499)
at
org.apache.felix.dm.impl.ComponentImpl.invokeAddOptionalDependencies(ComponentImpl.java:1444)
at
org.apache.felix.dm.impl.ComponentImpl.performTransition(ComponentImpl.java:1031)
at
org.apache.felix.dm.impl.ComponentImpl.handleChange(ComponentImpl.java:961)
at
org.apache.felix.dm.impl.ComponentImpl.lambda$2(ComponentImpl.java:403)
at
org.apache.felix.dm.impl.ComponentImpl$$Lambda$2/1359869532.run(Unknown Source)
at
org.apache.felix.dm.impl.SerialExecutor.runTask(SerialExecutor.java:138)
at
org.apache.felix.dm.impl.SerialExecutor.runTasks(SerialExecutor.java:120)
at
org.apache.felix.dm.impl.SerialExecutor.execute(SerialExecutor.java:86)
at
org.apache.felix.dm.impl.SerialExecutor.execute(SerialExecutor.java:105)
at org.apache.felix.dm.impl.ComponentImpl.start(ComponentImpl.java:401)
at
org.apache.felix.dm.impl.ComponentScheduler.add(ComponentScheduler.java:69)
at org.apache.felix.dm.DependencyManager.add(DependencyManager.java:175)
...
{code}
> Improve the Javadoc for org.apache.felix.dm.ComponentStateListener
> ------------------------------------------------------------------
>
> Key: FELIX-5403
> URL: https://issues.apache.org/jira/browse/FELIX-5403
> Project: Felix
> Issue Type: Improvement
> Components: Dependency Manager
> Affects Versions: org.apache.felix.dependencymanager-r8
> Reporter: Dobias van Buuren
> Assignee: Pierre De Rop
> Fix For: org.apache.felix.dependencymanager-r9
>
>
> The class level javadoc in org.apache.felix.dm.ComponentStateListener still
> mentiones the methods from the DM 3 version of the ComponentStateListener
> interface (starting, started, stopping and stopped).
> Those methods aren't available anymore in the DM 4 version.
> It would be nice if this gets corrected in a newer version, because it is not
> trivial what the alternatives in org.apache.felix.dm.ComponentState are.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
