Hi Betrand, Am Montag, den 17.12.2007, 10:04 +0100 schrieb Bertrand Delacretaz: > On Dec 15, 2007 10:19 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > > > ...Am Mittwoch, den 12.12.2007, 17:00 +0100 schrieb Bertrand Delacretaz: > > > One important goal is being able to drop a microsling application... > > > > The classical bootstrap problem. In Sling we solved this with a initial > > content load support in the jcr/resource project.... > > Do you have a suggestion for how to solve that in microsling, i.e. > without using OSGi bundles?
Not at all because it is not required. The point in this discussion is: We have microsling with an empty repository. As soon as content is dropped into the repository, this discussion probably does not apply anymore. > A simple mechanism might be to detect (with JCR observation) when > *.sysview.xml files are loaded into the repository, and import them > automatically. > > Or, more flexible, define a script name pattern that is executed > automatically when copied into the repository (I'm sure many of us > would love to have this called AUTOEXEC.js ;-). This script could > create the required initial content nodes when an application is > dropped into microsling. I don't think, that this is a good idea ! In Sling we use Bundles which have defined lifecycles and respective events. We should not invent yet another lifecycle mechanism with all its consequencese etc. In fact it is not required, because as I noted above, as soon as content is in the repository, this thread does not apply any more. How content is getting into the repository is not the core task of microsling (Of course the DefaultServlet or some registered servlet might be capable of accepting a request for content setup. But this is another story). Regards Felix
