On Dec 17, 2007 11:05 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Am Montag, den 17.12.2007, 10:04 +0100 schrieb Bertrand Delacretaz: > > ...A simple mechanism might be to detect (with JCR observation) when > > *.sysview.xml files are loaded into the repository, and import them > > automatically.... > ...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.... Ok, so maybe I wasn't clear on the usage scenario. The overall goall is to allow users, without using any tools other than a set of application files, a WebDAV client and a web browser, to copy and start a microsling application, here's the scenario: 1. User starts microsling and mounts the JCR repository via WebDAV 2. User copies a collection of script files , which represent a microsling application, into the repository (under /apps by convention). 3. User wants to start working with the application, but some initial content nodes must be created for that to work. At step 3, the required content nodes might need to be created with specific sling:resourceType values, and that's not possible via WebDAV. So, some form of content loading/initialization mechanism is needed: either some bootstrapping scripts, which can create the required Nodes, or some files containing node data, which are loaded automatically. -Bertrand
