Bertrand Delacretaz wrote: > Not really "at the same time", IMHO the sequence is, in a typical > Sling launchpad setup: > > 1. OSGi framework starts > 2. Sling engine bundle starts (few dependencies, so starts early) - > HTTP requests are accepted now, or soon > 3. SlingRepository becomes available (usally later- more dependencies > and heavier) > 4. jcrinstall observer requires SlingRepository, so starts even later > 5. jcrinstall configs might take 1-2 seconds to be activated, due to > some internal polling cycles > > So, if a request comes in afer step 2, and at step 5. some additional > SystemStatus configs would have come in, we have a problem. Yes, sure but if you think of the initial provisioning, where jcr install (or any other install routine) installs the sling bundles and adds the config. From there one everything is fine and before that nothing is available anyway. You only ran into the above if sling is already installed and then jcr install should provide the config. But as long as the config is installed at the same point of time as the status check service we're fine. And that should be easy.
> > What's wrong with that? You say "no, we must use ConfigAdmin" but > what's the justification for this? The above is more flexible and > copes with different use cases for the Sling engine, including not > having a repository and not having a ConfigAdmin service. > >> ...So I withdraw my +1 for properties :) and give +1 for config admin!.. > > I'm starting to think this thread is a plot to make me lose the few > hair that I have left ;-) > Ah, damn, you recognized this too early...now you spoiled all the fun :( We have a bet running how long it will take you to reach that state :) Ok, seriously, sling.properties are problematic as they are only available if sling is run with the launchpad. If you run sling inside equinox, spring server etc. the properties are not available! When I gave my +1 for the properties I didn't thought if this myself. But then during the whole discussion I realized this :) So we should really use a standard way that works in every installation. Carsten -- Carsten Ziegeler [email protected]
