[
https://issues.apache.org/jira/browse/SLING-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13598689#comment-13598689
]
Bertrand Delacretaz commented on SLING-2782:
--------------------------------------------
AFAICS this is not backwards compatible, as currently the node type is set by
the repository if not specified.
The following content structure looks fairly natural to me:
myPage (nodetype app:page)
jcr:content (nodetype nt:unstructured, resourceType app/page)
but here you might create the jcr:content node with nodetype app:page which is
not what you want
> Try to use sling:resourceType as a node type for node creation
> --------------------------------------------------------------
>
> Key: SLING-2782
> URL: https://issues.apache.org/jira/browse/SLING-2782
> Project: Sling
> Issue Type: Improvement
> Components: JCR
> Affects Versions: JCR Resource 2.2.4
> Reporter: Carsten Ziegeler
> Fix For: JCR Resource 2.2.6
>
>
> Right now, creating resources through the resource API
> (ResourceResolver#create) still requires some knowledge about the underlying
> storage especially in the case of JCR - in many cases you need to provide the
> primary node type.
> We could relax this and use the sling:resourceType as the node - but only if
> jcr:primaryType is not specified and sling:resourceType contains a valid node
> type name.
> This is in line with the implementation of the resource type handling for jcr
> resources: if the node does not have a sling:resourceType, the node type is
> returned.
> In addition, we defined that e.g. for files all resource providers should
> return nt:file as the resource type and nt:folder for folders. So making this
> work the other way round, fits into this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
