Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
JCR Resource 2.2.4
-
None
Description
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.