[
https://issues.apache.org/jira/browse/SLING-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-663.
-----------------------------------
Resolution: Fixed
After changing the node type definition in Rev. 697080, any node is allowed
again below sling:Folder, yet the default node type is sling:Folder.
Integration tests now run smoothly (except the JSONRenderer test on some
systems, but this is a different issue...)
> Make sling:Folder more folder like
> ----------------------------------
>
> Key: SLING-663
> URL: https://issues.apache.org/jira/browse/SLING-663
> Project: Sling
> Issue Type: Wish
> Components: JCR Resource
> Affects Versions: JCR Resource 2.0.2
> Reporter: Tobias Bocanegra
> Assignee: Felix Meschberger
> Fix For: JCR Resource 2.0.4
>
>
> the current sling:Folder looks like this:
> [sling:Folder] > nt:hierarchyNode, nt:unstructured
> orderable
> + * (nt:base) = sling:Folder version
> this is very convenient since it allows all kind of properties and nodes.
> But imo it's wrong that it is orderable. since folders dont have an
> order (at least in no FS is know).
> furthermore, i find it 'wrong' to allow * child nodes. if you want to
> add an arbitrary child node to a folder, we should use the
> sling:HierarchyNode mixin. as for the * properties, i think they are ok and
> should stay.
> the only inconvenience about nt:folder is, that is does not define a
> default primary type.
> so i suggest to change sling:Folder to:
> [sling:Folder] > nt:folder
> - * (undefined) multiple
> - * (undefined)
> + * (nt:hierarchyNode) = sling:Folder version
> and add:
> [sling:HierarchyNode] > nt:hierarchyNode mixin
> [sling:OrderedFolder] > sling:Folder orderable
> + * (nt:hierarchyNode) = sling:OrderedFolder version
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
