[
https://issues.apache.org/jira/browse/SLING-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592752#action_12592752
]
Carsten Ziegeler commented on SLING-367:
----------------------------------------
Ok, rethinking the issue, I still would prefer to separate between
something which is stored in the repo during a post and something that
has an influence on how/what is stored. Using the prefix "sling" for
node types, node and property names seems to be the best choice.
What about just using a ":" for prefixing commands? It then looks like
a command shell with a command (ok, sort of at least) ":move" etc.
It's short, can be easily explained and avoids collisions.
> 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: Post Servlets
> 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.
