Hi Robert,
thanks for the reference, SLING-6305 is partly this problem (but not
only as it seems). I fully agree with Felix's comment "I suggest to
attack the problem at the right place" [1] though.
My proposal: We change the provisioning model in a way that all
mentioned configurations become active exactly with the start level of
org.apache.felix.configadmin. As this is the case from second startup on
anyway, I suppose there is a very low risk of regressions (I created [2]
for that.). The same probably has to be changed for the new feature
model (I haven't looked into that yet).
-Georg
[1]
https://lists.apache.org/thread.html/4bc835e3e1d5ffe97fbb7ef7b6a7db02598f313bd2bf708b938b4eef@%3Cdev.sling.apache.org%3E
[2] https://issues.apache.org/jira/browse/SLING-8355
On 2019-04-12 10:49, Robert Munteanu wrote:
Hi Georg,
On Fri, 2019-04-12 at 00:47 +0200, Georg Henzler wrote:
Hi all,
I'm trying to add a config to the provisioning model [1] that is
active
during first startup at startlevel 5. Looking at [2] this does not
seem
to be possible (or it's not documented). On second startup it's fine
since the config is there, but on first startup, the config is only
created at startlevel 30 (there is a log for "CM Event Dispatcher"
that
shows this). Moving the config to boot.txt also does not work. Not
sure
why the configs are only made active that late on first startup,
configadmin would be available from startlevel 1 and from second
start
on the configs are available early anyway...
Maybe related to https://issues.apache.org/jira/browse/SLING-6305 ?
Robert
