On Mon, Jun 15, 2009 at 1:42 PM, Carsten Ziegeler<[email protected]> wrote: > The stuff Alex suggests is similar to the idea we discussed some time > ago when we first thought about this. > If we use some kind of configuration for this check, the questions is > when is this configuration available? If first the engine starts, the > check is performed (with an empty or minimal configuration) you have > a system which is running, then at a later point the config kicks in > and your system is not ready anymore until the required stuff is running. > This might be nitpicking but the system might appear as ready although > its not.
Right, the repository might be such a problem. See below. > As a general note, checking if the system is ready might increase the > startup time as you're system is only responding if all required > services are really available. There might be cases where this is not > necessary. Well, that's why it is configurable ;-) An empty config would mean system is ready immediately (when the engine is up and running). > Regardless of what we do, I think that the ready check and the > configuration for this check must form a single unit. Therefore > additional configuration and extra bundles are not a good solution in my > opinion. To be fair, I have not good idea either atm. > > But let's add some other requirements :) The stuff must work without a > repository (again my use case for portlets do not have a repository) and > it should work without third bundles like config admin etc. > Therefore a check like Alex suggest above which solely relies on the > OSGI API seems to be good start; the remaining question however is the > configuration therefore. Right, if the repository is optional, one could simply make an OSGI config out of it. This way we can control it via jrcinstall and config nodes in the repository, if present, or resort to webconsole and standard Felix config for non-repository based Sling instances. Regards, Alex -- Alexander Klimetschek [email protected]
