You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "angela (JIRA)" <ji...@apache.org> on 2019/02/15 13:45:00 UTC
[jira] [Resolved] (OAK-8049) AbstractSecurityTest: fix
PartialValueFactory field and it's usages.
[ https://issues.apache.org/jira/browse/OAK-8049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
angela resolved OAK-8049.
-------------------------
Resolution: Fixed
Fix Version/s: 1.11.0
1.12
Committed revision 1853645.
> AbstractSecurityTest: fix PartialValueFactory field and it's usages.
> --------------------------------------------------------------------
>
> Key: OAK-8049
> URL: https://issues.apache.org/jira/browse/OAK-8049
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, security
> Reporter: angela
> Assignee: angela
> Priority: Major
> Fix For: 1.12, 1.11.0
>
>
> [~mreutegg], with OAK-7569 you introduced a new protected field for {{PartialValueFactory}} in the {{AbstractSecurityTest}}, which is unfortunately name {{valueFactory}}. This disguises the fact that it is not a regular {{ValueFactory}} as exposed by {{getValueFactory(Root)}}. Also it is created with the default {{NamePathMapper}} instead of creating it on demand based on {{getNamePathMapper}}, which might be an implementation containing local namespace mappings.
> [~stillalex], unless you object I am going to rework that part of the {{AbstractSecurityTest}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)