Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
JCR API comes with 2 ways of adding new child nodes:
- Node.addNode(String, String) [0]
- Node.addNode(String) [1]
[0] https://docs.adobe.com/content/docs/en/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/Node.html#addNode(java.lang.String,%20java.lang.String)
[1] https://docs.adobe.com/content/docs/en/spec/javax.jcr/javadocs/jcr-2.0/javax/jcr/Node.html#addNode(java.lang.String)
the second variant leaves the detection of the primary type to the implementation. However, omitting the primary type with repo-init create path is IMHO not possible. there needs to be a default primary type or a explict primary type defined with the individual segment.
Attachments
Issue Links
- relates to
-
SLING-10219 Expand enforcing principal-based authorization option to repo-init
- Closed