You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2008/04/05 10:17:24 UTC
[jira] Reopened: (SLING-354) Better way to define the node name for
a newly created node
[ https://issues.apache.org/jira/browse/SLING-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bertrand Delacretaz reopened SLING-354:
---------------------------------------
Assignee: (was: Carsten Ziegeler)
> Better way to define the node name for a newly created node
> -----------------------------------------------------------
>
> Key: SLING-354
> URL: https://issues.apache.org/jira/browse/SLING-354
> Project: Sling
> Issue Type: Improvement
> Components: ujax
> Reporter: Carsten Ziegeler
> Fix For: 2.0.0
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> The current node name generator checks for a fixed set of request parameters name. While this approach is fine, it creates a problem as even if one of those properties is used to define the name, it is later on still tried to be set as a parameter.
> I propose to add a sling:post:nodeName property to define the name.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.