Hello,

I have a bit of strange problem and I'm hoping somebody reading has
experienced something similar and can tell me where I'm going wrong.

I'm registering a number of services that are proxies, these show up in the
console and I can use the framework API to look up valid references and
invoke methods.

The problem is these aren't being picked up by SCR managed components -
they just show as unsatisfied.  I replaced the proxies with a concrete
implementation (non-DS, framework registered) and the dependencies were met
and the DS components activated - so everything appears to work
independently, but not in concert it seems.

I am creating and registering these services via a SCR managed component
but not in any lifecycle methods.  Just using standard
java.lang.reflect.Proxy#newProxyInstance() with hacky custom classloader
that simply delegates to the bundles exporting the various
interfaces/classes used in the proxied interfaces.

Also tried to create a simple test case with pax-exam but I'm unable to
reproduce it there.


I'm at loss looking at my own code, so will start digging into the Felix
SCR code to understand how it uses the framework API to find 'n' bind,
hopefully that will shed some light on my problem.


Any suggestions gratefully received, thanks for listening,


regards,
Caspar

Reply via email to