You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tobias Bocanegra (JIRA)" <ji...@apache.org> on 2008/04/09 05:59:25 UTC

[jira] Commented: (SLING-367) change sling:post: to sling: for "command" prefixes in form names

    [ https://issues.apache.org/jira/browse/SLING-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587041#action_12587041 ] 

Tobias Bocanegra commented on SLING-367:
----------------------------------------

if this is changed to "sling:" i would ignore all the commands explicitly as value input instead of the general 'startsWith("sling:")' mechanism as it is implemented in todays SlingPostServlet. so at least the "sling:resourceType" does not need to be prefixed with "./"

but basically: +1 for using "sling:"

> change sling:post: to sling: for "command" prefixes in form names
> -----------------------------------------------------------------
>
>                 Key: SLING-367
>                 URL: https://issues.apache.org/jira/browse/SLING-367
>             Project: Sling
>          Issue Type: Bug
>          Components: ujax
>            Reporter: David Nuescheler
>
> I think it is fair to also prefix the form elements that express certain "commands" 
> with "sling:" since they are sling related. 
> i see it more as a side effect that the "sling:resourceType" also gets persisted.
> generally, i think everything that has something to with "sling" should be prefixed
> with "sling". 
> I think we need to make sure that we don't complicate the most simple cases just
> to a avoid possible collisions

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.