[
https://issues.apache.org/jira/browse/SLING-2986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804079#comment-13804079
]
Gilles Knobloch commented on SLING-2986:
----------------------------------------
{quote}
Gilles Knobloch What's your use-case for marking a resource as merged? I can
only imagine corner cases like e.g. building a UI to edit such resources. Would
it be acceptable to identify the source (resource provider) in the
ResourceMetadata?
{quote}
One use case is a UI to ease editing/simulating of this resources (probably in
a far future though...)
Using {{ResourceMetadata}} might be fair enough for now.
{quote}
One more thing: IMHO {{sling:hideChildren}} should be a {{String[]}}, and work
just like {{sling:hideProperties}}. This would be more flexible than making it
boolean.
{quote}
Good idea. Will update my implementation.
> Merged Resource Provider
> ------------------------
>
> Key: SLING-2986
> URL: https://issues.apache.org/jira/browse/SLING-2986
> Project: Sling
> Issue Type: New Feature
> Components: ResourceResolver
> Reporter: Gilles Knobloch
>
> As exchanged once with Felix Meschberger, the idea is to implement a custom
> resource provider, with ability to merge multiple resources based on your
> search paths.
> For instance, if your search paths are
> /apps
> /libs
> Hitting /merge/my/resource/is/here will check
> /apps/my/resource/is/here
> /libs/my/resource/is/here
> There are some options like:
> - add/override property
> - delete a property of the resource under /libs
> - reorder nodes if available
> I intend to submit this patch as soon as possible.
> Code is currently located at https://github.com/gknob/sling-resourcemerger
--
This message was sent by Atlassian JIRA
(v6.1#6144)
