[ https://issues.apache.org/jira/browse/SLING-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590247#action_12590247 ]
Tobias Bocanegra commented on SLING-386: ---------------------------------------- you need to read the response of the first post in order to figure out what node was created and use this for subsequent request. additionally i think that the 2nd post should fail, since the xyz is not a valid jcr name. suggest to "close invalid" > rules for creating node names should be uniform > ----------------------------------------------- > > Key: SLING-386 > URL: https://issues.apache.org/jira/browse/SLING-386 > Project: Sling > Issue Type: Improvement > Reporter: Michael Marth > > I have an issue when nodes are created through a form post: consider that I > have a weird string xyz that is not fit as a JCR node name, e.g. because it > contains umlauts or slashes or so. > If I do a post to /content/mynode/* > and give this parameter > name=xyz > this is used as a name hint and xyz is converted something sane (let's call > it xyy_conversion1) > In the next step I want to post to /content/mynode/xyz/* > in order to create a child node of xyz > It seems that in these two cases xyz is converted differently. Thus, in my > example above the second post would not create a child node of the first one, > but rather something like: > -content > |-mynode > |- xyy_conversion1 > |- xyz_conversion_2 > |- node_from_second_post > the conversation algorithms should be the same in both cases -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.