Marcel Offermans (JIRA) wrote:
About asynchronously starting for bundles with long running start methods, you now spawn a new thread and use that to call activateServiceInternal() which does many things, including invoking "init" and "start" methods. My main concern here is that I don't think this is a problem that should be solved by the dependency manager. If your service implementation does lengthy operations in its "init" or "start" methods, it should spawn a background thread there (this is in my opinion similar to the way the OSGi spec deals with this in the "start" of the bundle activator).
I agree with Marcel. It seems like this type of feature should be implemented by the services that need it and not part of the dependency manager core.
-> richard