sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Pauls (JIRA)" <>
Subject [jira] [Commented] (SLING-8411) Provide a way to bifurcate a repository path to a provider mount
Date Thu, 16 May 2019 08:59:00 GMT


Karl Pauls commented on SLING-8411:

[~cziegeler], I agree. Furthermore, I guess there is no problem with waiving the marker interface
requirement at a later point and just start out with it at this point (to be save). I'll wait
until tomorrow and if there are no objections I'll merge the PR as it is at this point. 

> Provide a way to bifurcate a repository path to a provider mount
> ----------------------------------------------------------------
>                 Key: SLING-8411
>                 URL:
>             Project: Sling
>          Issue Type: Improvement
>          Components: JCR
>    Affects Versions: JCR Base 3.0.6
>            Reporter: Karl Pauls
>            Assignee: Karl Pauls
>            Priority: Major
>             Fix For: JCR Base 3.0.8
>          Time Spent: 10m
>  Remaining Estimate: 0h
> While one would normally use a resource provider to extend the content tree, sometimes,
that can be not enough a code might make assumptions about the resources being actually being
backed by JCR. This can be problematic as for example, a given resource can not necessarily
be adapted to a Node nor be found via a Session.
> Hence, a similar approach on the JCR level allowing developers to mount content into
sub trees of the repository itself can be helpful to be able to support these kind of usecase.
We should provide a hook for a repository mount that takes over a given subpath by wrapping
repositories returned by the base and dispatching to the mount when the request is for a given

This message was sent by Atlassian JIRA

View raw message