[
https://issues.apache.org/jira/browse/SLING-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gilles Knobloch updated SLING-3397:
-----------------------------------
Attachment: SLING-3397.patch
I think this has to be done through a service, and not just a utility class.
Indeed, you need to get the value of the merge root path and access to resolver
search paths (which you could solve through passing the resolved as first
argument - but merge root path would still be missing).
My proposal is to make the {{ResourceProviderFactory}} implement a new service
{{ResourceMergerService}}, which contains the 3 methods [~cziegeler] proposed.
Misc:
* Fixed {{"sling.mergedResource}} as metadata flag instead of
{{sling.mappedResource}} - I guess it's a typo from my initial patch
* Fixed an issue in how the merge root path is initialized if it ends with a
{{/}}
I tested the provided patch in my application and it seems to work fine.
> Provide a way for path operations
> ---------------------------------
>
> Key: SLING-3397
> URL: https://issues.apache.org/jira/browse/SLING-3397
> Project: Sling
> Issue Type: Improvement
> Components: Extensions
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: Resource Merger 1.0.0
>
> Attachments: SLING-3397.patch
>
>
> With the resource merger we have a new resource provider which is mounted
> somewhere in the resource tree.
> While the resource resolver has a method to get the search path, there is no
> way to find out, the mnt point for the resource merger.
> In addition, in some cases you already have a resource from within a search
> path and you want to access the merged resource
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
