Hi, I haven't thought about this yet :)
But I would prefer 1) although that raise some interesting questions, especially as intermediate nodes might end up to be persisted in different storages Carsten 2012/7/6 Bertrand Delacretaz <bdelacre...@apache.org>: > Hi, > > Looking at the SLING-2530 Resources CRUD stuff - for the create > operation, https://cwiki.apache.org/confluence/display/SLING/Supporting+CRUD > says > >> We add a new method create(String absolutePath, ValueMap properties) to the >> resource resolver, where the value map is optional. >> This will create the resource at the given path and add the provided >> properties. > > I see two potential problems: > > 1) If the parent of the Resource to create does not exist yet, options > might be needed to specify how to create the intermediate path - the > node type to use for intermediate nodes in JCR, for example. > How can those options be specified? > > 2) If this requires the parent Resource to pre-exist, it would be > clearer to express that as a createChild method on the Resource object > > Carsten, how do you see that in your design? > > -Bertrand -- Carsten Ziegeler cziege...@apache.org
