[jira] [Commented] (SLING-11455) ResourceResolver Mock: ResourceProvider implementation

["Mahidhar Chaluvadi (Jira)" <ji...@apache.org>]

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

Mahidhar Chaluvadi commented on SLING-11455:
--------------------------------------------

[~sseifert] - 1 Question on the changes captured in this PR. RRMockResourceResolverWrapper is not available for public use, and when we obtain resource resolver using context, they are always instances of this Wrapper class and not the underlying wrapper instance i.e. MockResourceResolver. So how does the ModifiableValueMap work for FS provider? Please let me know if you want me to do any tests and share the results. Thanks

> ResourceResolver Mock: ResourceProvider implementation
> ------------------------------------------------------
>
>                 Key: SLING-11455
>                 URL: https://issues.apache.org/jira/browse/SLING-11455
>             Project: Sling
>          Issue Type: New Feature
>          Components: Testing
>            Reporter: Stefan Seifert
>            Assignee: Stefan Seifert
>            Priority: Major
>             Fix For: Testing ResourceResolver Mock 1.4.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> ResourceResolver Mock currently supports only directly creating a mocked ResourceResolver instances, which is fine for most testing use cases. however, since introduction of SLING-5922 we allow mounting of additional test resources into the resource tree via FSResourceProvider, and are currently using a rough hand-build intergration of MockResourceResolver and this resource provider. this has some flaws and unwanted side-effects, SLING-10937 is one of it.
> we need a ResourceProvider implementation as alternative, backed by all the existing functionality.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)