[
https://issues.apache.org/jira/browse/SLING-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-394:
------------------------------------
Description:
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.
was:
since i have not seen a usecase where it would be helpful to specify the
saveParamPrefix to something
different than "./" i would recommend that we remove this option.
does someone have a good usecase for that?
Issue Type: Improvement (was: Bug)
Summary: Remove ":savePrefix" support (was: remove
"sling:post:saveParamPrefix";)
> 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.
