Hi all,
I've been playing with DependencyManager recently and I must say i find
the design and syntax extremely elegant and also much more traceable
than the SCR.
So much so that I was about to remove all my DeclarativeService XMLs to
replace them with a few lines of DependencyManager when i bumped into an
issue: I sometimes have a dependency on a class (as opposed to an
interface), but this is made impossible in DependencyManager because of
the use of proxies.
Here's a typical error i get when i try to bind a specific classloader:
java.lang.IllegalArgumentException: java.lang.ClassLoader is not an
interface
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:362)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
at
org.apache.felix.dependencymanager.ServiceDependency.getNullObject(ServiceDependency.java:96)
But i guess it would be the same if i was to bind any implementation of
an abstract class.
I'd be quite sad to have to abandon DependencyManager for this reason..
Does anyone know of a workaround, or a future release that would address
this issue?
Thanks,
Arjun
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
