[
https://issues.apache.org/jira/browse/SLING-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649358#comment-13649358
]
Alexander Klimetschek commented on SLING-2853:
----------------------------------------------
> As we want to allow additional properties for a member, I wouldn't go with a
> multi-value property,
> especially not with allowing both, a multi-value property defining the
> collection and child nodes.
> This adds unnecessary complexity.
If you look at the code, it's actually simpler. The current code already relies
on the "pathorder" property for the order, which needs to keep all references
anyway for it to work.
> like sending collection events. We can clearly define in the API that
> collections should be deleted through the manager.
I think it should all work fine using the sling post servlet or any other
mechanism creating the right structure through other means outside the
collection API. So the ResourceCollectionManager and ResourceCollection are in
a way central utilities to easily create the right structure, but central would
always be the underlying content structure maintained through the
infrastructure layer of the resource provider (e.g. jcr).
> What about applying the current patch and then discussing the things one
> after the other
Ack.
> Add ResourceCollection to Sling
> -------------------------------
>
> Key: SLING-2853
> URL: https://issues.apache.org/jira/browse/SLING-2853
> Project: Sling
> Issue Type: New Feature
> Components: API
> Affects Versions: API 2.0.2
> Reporter: Amit Gupta
> Priority: Minor
> Attachments: collection.zip, resourcecollection.zip
>
>
> Creating a collection of resources has been a use case for a while and there
> has been no inherent support in SLING for the same.
> This proposal is to add a ResourceCollection interface and implementation
> that allows creation of collection of resources.
> Collection is a simple list of members, where each member contains path of
> resource it refers to. In future, we might need to store additional
> information with the member, hence following structure is proposed
> N: resourceCollection (nt:unstructured)
> + P: sling:resourceType
> + N : members (nt:unstructured)
> + N: member_res1 > nt:unstructured
> + P: path > string, reference to actual resource
> + N: member_res2 > nt:unstructured
> + P: path > string, reference to actual resource
--
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
