I mostly agree with Bertrand's interpretation. However, I a config can be applied early (i.e. registered with config admin), but components are still lazily instantiated. Does anyone know if there is a guarantee that components are configured (activated) before they become visible?
If there is no such guarantee, there may be a time-window when they are visible with default config before they are properly configured. Regards Julian PS: I just committed an experimental change to set whitelist.bypaass=true in order to rule out any regexp issues. On Tue, Nov 29, 2016 at 9:36 AM, Bertrand Delacretaz <[email protected]> wrote: > On Mon, Nov 28, 2016 at 10:47 PM, Robert Munteanu <[email protected]> wrote: >> ...That would be SLING-6305 [1] I guess. ... > > I haven't debugged deep down yet but intuitively it should be possible > to apply very early in the startup phase all the configs that are > supplied by the provisioning model. > > If someone has time to look at why this is not the case that might > help solve a number of similar issues + avoid multiple component > restarts when configs appear late. > > -Bertrand
