[
https://issues.apache.org/jira/browse/SLING-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617746#action_12617746
]
Lars Trieloff commented on SLING-588:
-------------------------------------
Sorry, this does not work due to the NullPointerException mentioned in the
original post.
Additionally it would be interesting to know why you would not change the
behavior. My proposed patch will not change the way existing content is
addressed, so the resolution between POST and GET scenarios will stay
consistent, the only difference is that resources will be addressed directly
through their URI, not indirectly through a generic RPC-like endpoint and the
specification of the resource that will be manipulated in the request entity.
> Sling ignores specified node path when creating content
> -------------------------------------------------------
>
> Key: SLING-588
> URL: https://issues.apache.org/jira/browse/SLING-588
> Project: Sling
> Issue Type: Bug
> Reporter: Lars Trieloff
> Attachments: SLING-588.patch
>
>
> As described here: http://markmail.org/message/u3be3mpaal4efngj Sling will
> ignore the node path specified in the HTTP request when creating contents
> which makes it impossible to create nodes with a dot in the node name from a
> form post.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
