[
https://issues.apache.org/jira/browse/SLING-11455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17581805#comment-17581805
]
Roy Teeuwen commented on SLING-11455:
-------------------------------------
[~sseifert] another unwanted effect of the RRMockResourceResolverWrapper is
that you can't set findResourcesQueryHandler and queryResourcesQueryHandler
instances by casting it to (MockResourceResolver) like shown in the docs. Now I
had to use reflection to get the wrapped resource resolver to set mocked
queries. Could this be taken into account as well when fixing this?
> 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: 2h
> 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)
