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 Schreiber (Jira)" <ji...@apache.org> on 2020/09/30 07:16:00 UTC

[jira] [Resolved] (OAK-9243) avoid potential NPE with Condition.Property

     [ https://issues.apache.org/jira/browse/OAK-9243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Angela Schreiber resolved OAK-9243.
-----------------------------------
    Fix Version/s: 1.36.0
       Resolution: Fixed

Committed revision 1882147.


> avoid potential NPE with Condition.Property
> -------------------------------------------
>
>                 Key: OAK-9243
>                 URL: https://issues.apache.org/jira/browse/OAK-9243
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, security
>            Reporter: Angela Schreiber
>            Assignee: Angela Schreiber
>            Priority: Minor
>             Fix For: 1.36.0
>
>
> {{Condition.Property}} in the user.query package should be split into 3 different subclasses for the 'exists', 'like' and 'value-comparison' conditions. this allows to avoid assigning null values to the relpath and value fields and thus making the usages more robust against NPE. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)