[
https://issues.apache.org/jira/browse/SLING-12779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17950345#comment-17950345
]
Konrad Windszus commented on SLING-12779:
-----------------------------------------
The ignore for {{jcr:mixinTypes}} was probably always be there but the reason
is unclear to me. Initially also {{jcr:primaryType}} was ignored but this is no
longer skipped since SLING-6595
(https://github.com/apache/sling-org-apache-sling-testing-sling-mock/commit/3cbf64d10c9c063ce85b3bbe52fc9a4737e25258).
[~sseifert] Any insights here?
> sling-mock: content loader should not ignore jcr:mixinTypes properties for
> any resource resolver mockny of the
> ---------------------------------------------------------------------------------------------------------------
>
> Key: SLING-12779
> URL: https://issues.apache.org/jira/browse/SLING-12779
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing Sling Mock 3.5.4
> Reporter: Konrad Windszus
> Priority: Major
>
> The property with name {{jcr:mixinTypes}} is ignored for any resource
> resolver mock type except {{JCR_OAK}}:
> https://github.com/apache/sling-org-apache-sling-testing-sling-mock/blob/6ea32b6d333777ec2057b0b072c22c4421d02a69/core/src/main/java/org/apache/sling/testing/mock/sling/loader/ContentLoader.java#L83.
> However this property is often crucial for tests which at run time leverage
> this property (as they assume a JCR resource resolver) however for
> performance reason just use a another resource resolver type than JCR_OAK.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
