Hi Am 15.07.2012 um 18:51 schrieb Reto Bachmann-Gmür:
> Hello > > In my app I'm configuring a service with a bundle providing its > configuration. Now it seems the components are first started without that > configuration and then restarted with it. Normally when configuration is available before the component is activated, it is activated with the configuration. If the configuration only becomes available later, the component is potentially reactivated with the configuration (potentially because the component may be declared to take configuration through a modified method). > As a consequence my app [1] > doesn't work correctly when started the first time. From the second start > up it works correctly as it doesn't first start the component with the > wrong configuration. > > Is there a way to make sure the components aren't started without the > provided configuration? Yes, you can declare the component to require component. Such components are only activated once configuration is available. As soon as the configuration is removed, the component is deactivated. Look for the "configuration policy" attribute. Regards Felix > > Cheers, > Reto > > 1. sling-stanbol-launcher in https://github.com/retobg/sling-stanbol
