[jira] [Comment Edited] (SLING-8411) Provide a way to bifurcate a repository path to a provider mount

["Karl Pauls (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839206#comment-16839206 ] 

Karl Pauls edited comment on SLING-8411 at 5/14/19 9:12 AM:
------------------------------------------------------------

??The limitation to the (implied) root mount and one other mount seems pretty arbitrary.??

It is. The reason is simply lack of time so for now it is a single mount which can be mounted to several mount points. However, there is no limiting factor (as far as I can see) in the current design that would prevent us from changing this to several mounts in the future. Would be a nice future work kinda thing.


was (Author: karlpauls):
?? The limitation to the (implied) root mount and one other mount seems pretty arbitrary.??

It is. The reason is simply lack of time so for now it is a single mount which can be mounted to several mount points. However, there is now limiting factor (as far as I can see) in the current design that would prevent us from changing this to several mounts in the future. Would be a nice future work kinda thing.

> Provide a way to bifurcate a repository path to a provider mount
> ----------------------------------------------------------------
>
>                 Key: SLING-8411
>                 URL: https://issues.apache.org/jira/browse/SLING-8411
>             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 subpath.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)