Methods would need to be added to the ResourceRegistry and ProvidersRegistry to allow dynamic deregistration. The ResourceRegistry might be easier than the ProvidersRegistry. I think the code is pretty safe to do the re-sorting of everything that needs to be done (i.e. since the get methods are already guarded by read locks), it's just that you would need to find the relevant records to delete and then do the re-sorting.
It may be something to consider for anyone doing any OSGi related work for bundles that go away. On Mon, Mar 29, 2010 at 9:46 AM, Jason Dillon <[email protected]> wrote: > I noticed there is a way to dynamically register new application classes via > RegistrationUtils, but is there also a way to deregister classes as well? > > --jason
