Community
Participate
Working Groups
The package org.osgi.framework.hooks.service defines the API for service registry hooks.
Assigning to BJ. BJ, I gave it a tentative target of 3.5 M3.
See http://www.osgi.org/download/osgi-4.2-early-draft.pdf for early draft which includes RFC 126.
I just committed support for RFC 126 section 5.2.2: Find Hooks. Support for RFC 126 section 5.1.1 has previously been committed.
I just commited support for PublishHooks. This involved moving all support for ServiceEvents into the serviceregistry package. I changed the PublishHook API definition to state the collection is of BundleContexts not Bundles. This change will be reflected in the RFC 126 design. This required new API for eventmanager package (isEmpty method and a copy constructor in EventListeners). I put @since 3.5 tags on the new methods, but I am not sure if that is sufficient for new API? All that remains now is ListenerHook support. This interface may also change as I get implementation experience...
I just committed the final code for the RFC 126 impl. This code added the ListenerHook support. Note: the ListenerHook interface has changed as a result of the implementation experience.