[
https://issues.apache.org/jira/browse/SLING-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763069#action_12763069
]
Justin Edelson commented on SLING-1137:
---------------------------------------
Well, it'd be best if there was a resolution to JCR-642 so as to avoid needing
to workaround the flat hierarchy problem. Although I firmly believe that a good
structure can be found in most cases, most != all.
+1 to the idea of making NodeNameGenerator pluggable.
> Support hierarchical child node creation from SlingPostServlet
> --------------------------------------------------------------
>
> Key: SLING-1137
> URL: https://issues.apache.org/jira/browse/SLING-1137
> Project: Sling
> Issue Type: Improvement
> Components: Servlets
> Reporter: Mark Baker
> Priority: Minor
>
> The default node creation functionality on "/" terminated paths via the
> SlingPostServlet doesn't scale very well as it only supports creation of
> nodes immediately under the targeted path. So, for example, when using this
> via a CQ form to capture form responses in the repository, a site can
> potentially have thousands of child nodes, leading to well known performance
> problems.
> I think it would be useful to offer an option for the servlet to save a
> hierarchy of nodes, perhaps via the common convention of using the first 4
> characters of the would-be node id to create a 2 level hierarchy.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
