[
https://issues.apache.org/jira/browse/OAK-644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13581403#comment-13581403
]
angela commented on OAK-644:
----------------------------
i didn't follow the other issue. can you provide addition information on how
you got there?
null privilege name doesn't makes too much sense and i don't see any reason why
you should get
there... so probably a bug or work-in-progress-artefact of the ac-work.
anyway: breaking is definitely wrong it is would lead to strange effects that
hard to track.
i will add a checkNotNull for the time being so we can track troubable some
code.
> Revisit PrivilegeDefinitionStore's use of null as a child name parameter
> ------------------------------------------------------------------------
>
> Key: OAK-644
> URL: https://issues.apache.org/jira/browse/OAK-644
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Affects Versions: 0.7
> Reporter: Alex Parvulescu
> Priority: Minor
> Attachments: OAK-644.patch
>
>
> As discussed on OAK-635, I'm extracting the PrivilegeDefinitionStore
> code&patch into a dedicated issue.
> Following the discussion on the dev list, I've filed it as a bug, as nulls
> are not considered valid input parameters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
