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 On Feb 17, 2014, at 11:13 AM, Guillaume Nodet <[email protected]> wrote: > The proxy is used for security reasons afaik. Mainly to secure commands. > We can't turn it off unless we disable security. > In fact, the proxy is not a blueprint thing, it's a proxy on the registered > osgi service. > > > 2014-02-17 18:17 GMT+01:00 Christian Schneider <[email protected]>: > I am using blueprint <service> to publish an object to the service registry. > > The problem is that instead of a service it seems to publish a proxy. So I > can not introspect the object. > I know that blueprint needs to inject a proxy if you use <reference> but why > does it also create a proxy when publishing a service. > Jean Baptiste showed me some code using ProxyManager to unproxy the object > but this is quite ugly and makes me depend on aries proxy. > > So why is the proxy created and can this be turned off? > > Christian > > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com > >
