On 14 Jan 2015, at 08:23, Christian Schneider <[email protected]> wrote:
>> How about using a special property for the routing proxy? Publish it with the same interface as the backend services but give it a service property like proxy=true. >> Then in the front end you can filter for a service with >> filter=(proxy=true)". This is the simple, straightforward, idiomatic way to do things. The only drawback is that all the clients need to specify that filter otherwise they are likely to get a backend injected instead of the proxy. "Timothy Ward" <[email protected]> write; > Also, if your service client is a DS component then these filters can be dynamically added/changed/removed using Configuration Admin. Thinking out loud: could one use a ListenerHook to detect service listeners binding to the service interface without filtering on the 'proxy' property and send them an "improved" filter via CA? Or would this be opening up another can of worms? Chris _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
