[
https://issues.apache.org/jira/browse/SLING-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16839201#comment-16839201
]
Karl Pauls commented on SLING-8411:
-----------------------------------
??in the test you register and retrieve Repository instances as RepositoryMount
services. This is confusing and it's not immediately obvious why and how this,
i.e. it violates the principle of least surprise.??
Well, it is a test with mocks - as such, I had not much choice. It was that or
create yet another wrapper. The implementation right now expects a service of
type RepositoryMount (I'll discuss that in another comment). I don't think the
element of least surprise applies for mock driven unit tests.
> 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)
