[
https://issues.apache.org/jira/browse/SLING-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12592401#action_12592401
]
Carsten Ziegeler commented on SLING-367:
----------------------------------------
I think there is a difference between stuff that is stored in the repository
and commands which perform some action on the repository.
Using the same prefix for both is imho confusing.
I don't really see why this complicates the simple use case - in the simple use
case, you might not need commands at all and just post stuff to change or add
content :) In addition, we have a client lib that hides this stuff anyway
(though I still don't think that it is complicated) :)
> 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.
