[
https://issues.apache.org/jira/browse/SLING-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597371#action_12597371
]
Bertrand Delacretaz commented on SLING-394:
-------------------------------------------
I'm ok to remove the :savePrefix support, I haven't seen a case where it's
actually needed, and if we really need it later it's easy to re-add while
staying backwards compatible.
> Remove ":savePrefix" support
> ----------------------------
>
> Key: SLING-394
> URL: https://issues.apache.org/jira/browse/SLING-394
> Project: Sling
> Issue Type: Improvement
> Components: Post Servlets
> Reporter: David Nuescheler
> Assignee: Felix Meschberger
> Priority: Minor
> Fix For: 2.0.0
>
>
> The :savePrefix parameter was intended to identify the required prefix to
> parameter names for them to be considered for content modification.
> The use case behind such prefixing is, that we might want to have forms which
> contain a mix GUI provided parameters (some GUI toolkits seem to add them)
> and parameters to be used for content update. In this case the content
> parameters could be prefixed and only those could be considered.
> In reality, the only value used for prefixing is "./" and the :savePrefix is
> never used. In fact, the SlingPostServlet's modification operation scans all
> parameters for some which are prefixed with "./" if the :savePrefix is not
> set and then decides upon using prefixes or not.
> Thus, this issue is about the following changes:
> * remove :savePrefix parameter support
> * the prefix used is hardcoded to be "./"
> * If any parameter with the prefix is found, only parameters starting with
> "./", "../" and "/" are considered for content update
> * If no parameter with the "./" prefix is found, all parameters not
> starting
> with the operation parameter prefix ":" are considered for content
> update.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
