[ https://issues.apache.org/jira/browse/SLING-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586026#action_12586026 ]
Carsten Ziegeler commented on SLING-354: ---------------------------------------- Ah ok, the current filtering of the other properties (like jcr:title etc.) makes the node name lower case, replaces spaces etc., so we would need a different filtering in this case. > Better way to define the node name for a newly created node > ----------------------------------------------------------- > > Key: SLING-354 > URL: https://issues.apache.org/jira/browse/SLING-354 > Project: Sling > Issue Type: Improvement > Components: ujax > Reporter: Carsten Ziegeler > Fix For: 2.0.0 > > Original Estimate: 0h > Remaining Estimate: 0h > > The current node name generator checks for a fixed set of request parameters > name. While this approach is fine, it creates a problem as even if one of > those properties is used to define the name, it is later on still tried to be > set as a parameter. > I propose to add a sling:post:nodeName property to define the name. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.