Bertrand Delacretaz wrote: > Now that I got your attention ;-) > > (warning: long read ahead) > > I've been working with David Nuescheler in the last few days, fixing > and improving a few things in microsling to allow him to build his > cool "your blog in 15 minutes" demo for javapolis [1]. > > This has brought a few issues to our attention, I'll explain them > here, comments are welcome. > > One important goal is being able to drop a microsling application (a > set of scripts, templates and static files) in the JCR repository (via > WebDAV), and start working without having to create any Nodes > beforehand. > > - o - > > ISSUE 1: Chicken and egg problem, resource not found intially -> map * > to SyntheticResource > > In one of the demos we create nodes under /content/linotype/posts > > So we direct people to > http://locahost:port/content/linotype/posts.html - but there's no > /content node yet, so the resource is not found. > > To solve this, SLING-129 implements SyntheticResource, and maps any > URL ending in * to one (that should be configurable, hardcoded using > regexps for now, see SyntheticResourceProvider). > > So now, http://localhost:port/content/linotype/posts/*.post.html > resolves to a SyntheticResource, which is empty and has an empty > resourceType. That page stores content under /content/linotype/posts, > everything's fine (almost, see issue 2). >
I haven't thought about all implications yet, but looking at the Atom publishing api, they use POSTs to the collection to create new childs which to me looks much nicer than the above url. Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
