In Core 4.3 we add EventListenerHook which replaces EventHook. It will let you filter at the listener level. This is currently implemented in the Equinox 3.7 builds if you wish to experiment with it. --
BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance hargr...@us.ibm.com office: +1 386 848 1781 mobile: +1 386 848 3788 From: Andreas Karlsson <andreas.karlsson...@gmail.com> To: osgi-dev@mail.osgi.org Date: 2011/02/12 19:55 Subject: [osgi-dev] EventHook flawed? Sent by: osgi-dev-boun...@mail.osgi.org Shouldn't EventHook let you filter a collection of listeners (something like ListenerHook.ListenerInfo) instead of contexts? That would enable you to examine the listener's filter and only let it see services based on a certain property. My case is that I want to control service visibility between customers of an application i.e. (customer.token=4kj53j-34kl3-some-token-234a). I want customers to share bundles but use their own services through ManagedServiceFactory. Is there another recommended way to achieve that? In any case, isn't it arguable that the EventHook would let you filter listeners instead of bundles? Best regards Andreas Karlsson _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
