You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Felix Meschberger (JIRA)" <ji...@apache.org> on 2008/09/17 21:01:47 UTC
[jira] Assigned: (SLING-663) Make sling:Folder more folder like
[ https://issues.apache.org/jira/browse/SLING-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Felix Meschberger reassigned SLING-663:
---------------------------------------
Assignee: Felix Meschberger
> Make sling:Folder more folder like
> ----------------------------------
>
> Key: SLING-663
> URL: https://issues.apache.org/jira/browse/SLING-663
> Project: Sling
> Issue Type: Wish
> Components: API
> Reporter: Tobias Bocanegra
> Assignee: Felix Meschberger
>
> 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.