Hi David and Chris,
I am not sure if we are talking about the same effect.
As I wrote in my original mail I am aware of the proxy that is created
when injecting a service using blueprint. It is necessary as blueprint
does the inject statically.
In contrast to this I am observing a proxy when I export the service. I
import the service using a service tracker. So I did not expect to
encounter a proxy for this case.
Guillaume mentioned the security layer as the source of the proxy. I
think this should also not apply. The etc/system.properties contains this:
karaf.secured.services = (&(osgi.command.scope=*)(osgi.command.function=*))
So while this should match for the commands it should not match for my
case where I simply export an Action without any properties. I will dig
a bit more.
Christian
Am 17.02.2014 20:59, schrieb David Jencks:
The proxy is a blueprint thing and as Chris says is there to damp
bouncing services. I think the DS technique of binding a replacement
service before unbinding the old one is a more appropriate solution to
this problem, although it certainly has different effects and produces
more bouncing.
thanks
david jencks
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
