[
https://issues.apache.org/jira/browse/SLING-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617787#action_12617787
]
Lars Trieloff commented on SLING-588:
-------------------------------------
If you could decide for a way of fixing the NPE, I would be glad to have a
working workaround. (and close this bug) However I still think it is quite easy
to find out which case the servlet is dealing with. As the user is free to
specify the action of the form, he can post to /some/sample if he wants no dot
and /some/sample.html if he wants a dot.
Speaking more broadly we are increasingly introducing "tricks", special cases
and magic post parameters to deal with a very specific use case "most of the
times in a CMS or such" while ignoring the needs of other use cases like DAM,
Blog, Wiki, social networking, forum, online shop, podcast, file sharing and
other content-centric web applications. Having a RESTful web application
framework implies in my opinion to respect concepts like Resource,
Representation, URI and to avoid RPC-like interaction if not necessary.
> 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.
