On 8/29/08, Alexander Klimetschek <[EMAIL PROTECTED]> wrote: > Hi all, > > I currently have the need to create a path by posting to the > SlingPostServlet, eg. /some/very/long/path, where only /some exists, > and very/long/path has to be created in the repo. Now I miss two > features in the current SlingPostServlet: > > a) specify only one intermediate jcr:primaryType (instead of > /some/very/jcr:primaryType=my:type, > /some/very/long/jcr:primaryType=my:type, etc.) for all the > intermediate nodes that have to be created are you able to specify the default nodetypes for new nodes in the nodetype of "/some" ? if yes, this should work automatically since the repository selects the correct nodetype.
> b) the path is built right from the user input, so I need a nameHint > path (eg. user enters "Verü/Lon g/Path", => pathHint = "/some/Verü/Lon > g/Path" sent to server, => generated node path is > "/some/ver_/lon_g/path"); I could do this on the client-side, but I > don't want to reimplement the nameHint -> valid name conversion, it's > good to have a central place for it but how would you differentiate from the case where a '/' is present in the hint but should not create deep paths? > A different solution would be to make several HTTP requests, one for > each node in the path, but this would also be more code complexity on > the client side and not transactional. > > WDYT? Overkill or nice-to-have feature? i would create the path clientsided... regards, toby
