[
https://issues.apache.org/jira/browse/SLING-295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12573880#action_12573880
]
David Nuescheler commented on SLING-295:
----------------------------------------
I would go with the jcr:primaryType aswell instead of a magic ujax:primaryType.
So far we used ujax: for things that don't have representation in content. I
think everything that has trivial representation in content should map the name
of the property directly to the form input name just make it simple to
understand.
I think it is intuitive for the user to use jcr:primaryType and other jcr:
properties.
In my mind jcr:mixinTypes for example should be treated like a normal
multivalue property, please don't introduce a special comma separated case for
that.
> Specify nodetype for node creation
> ----------------------------------
>
> Key: SLING-295
> URL: https://issues.apache.org/jira/browse/SLING-295
> Project: Sling
> Issue Type: Improvement
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Attachments: patch.txt
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> It would be nice to specify the node type for new nodes when they are created
> through the post servlet.
> Perhaps by specifying a node type parameter (like ujax:nodetype)?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
