You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2014/02/18 08:51:22 UTC
[jira] [Resolved] (SLING-3397) Provide a way for path operations
[ https://issues.apache.org/jira/browse/SLING-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler resolved SLING-3397.
-------------------------------------
Resolution: Fixed
Thanks for your patch, Gilles.
I've applied a slightly modified version which also corrects the name of the other metadata entry (from sling.mappedResources to sling.mergedResources)
> 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)