You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2018/08/27 08:40:00 UTC
[jira] [Closed] (SLING-7839) sling-mock: Import jcr:uuid property
in ContentLoader for resource resolver types that support it
[ https://issues.apache.org/jira/browse/SLING-7839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert closed SLING-7839.
---------------------------------
> sling-mock: Import jcr:uuid property in ContentLoader for resource resolver types that support it
> -------------------------------------------------------------------------------------------------
>
> Key: SLING-7839
> URL: https://issues.apache.org/jira/browse/SLING-7839
> Project: Sling
> Issue Type: Improvement
> Components: Testing
> Affects Versions: Testing Sling Mock 2.3.0
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Priority: Major
> Labels: mocks
> Fix For: Testing Sling Mock 2.3.2
>
>
> currently the ContentLoader implementation always ignores properties with {{jcr:uuid}} property, because it's not possible to set a uuid manually when creating nodes in via the JCR API in a real oak repository.
> but this restriction only applies when using the JCR_OAK resource resolver type - for the other types, especially RESOURCERESOLVER_MOCK and JCR_MOCK, this should be allowed to support unit tests relying on uuid versions present.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)