On Mon, 2016-11-21 at 14:14 +0100, Bertrand Delacretaz wrote: > On Mon, Nov 21, 2016 at 11:25 AM, Felix Meschberger <[email protected] > om> wrote: > > ...I assume you have a provisioning problem in that the bundles are > > started and > > thus the components activated *before* the configuration is > > actually stored > > in Configuration Admin.... > > I also think configurations should be active very early in the Sling > startup - if they are provided in the provisioning model they are > available right from the start.
That's something which is not 100% clear to me - why are they not available from the start. The configadmin and osgi installer bundles are available early in the process, definitely before the repository is up so the LoginAdministrativeWhitelist component should start with a configuration available. I think a hint is present in Carsten's comment from [1] > the issue here is that the support for configurations is available after the OSGi installer already started its work. The installer is happily installing bundles and only once that is done completely it picks up the configuration support which was registered while it was installing the bundles Robert [1]: https://issues.apache.org/jira/browse/SLING-5779?focusedCommentId= 15329297&page=com.atlassian.jira.plugin.system.issuetabpanels:comment- tabpanel#comment-15329297
