Hi Bertrand On Thu, Oct 27, 2011 at 11:39 AM, Bertrand Delacretaz <[email protected]> wrote: ... > There's probably a better way of solving that, for example using > service factories so that a service is only instantiated when its > configuration becomes available. The RequestLoggerService [1], for > example, uses this pattern with ConfigurationPolicy.REQUIRE.
The difference to the RequestLoggerService usecase is that I want to configure a service provided by a bundle I would rather not modify. I now set the startlevel of this bundle to 23 an thus higher to the default startlevel. It now seems to work, not sure if this is just luck and asynchronous starting could cause the startlevel 23 bundle service to effectively be started before it is the activator of the startlevel 20 bundle completed. Cheers, Reto
