[
https://issues.apache.org/jira/browse/SLING-8066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16683277#comment-16683277
]
Pankaj Parashar commented on SLING-8066:
----------------------------------------
[[email protected]], Yes, you are correct, the real jcr implementation
removes property if set null. This behaviour should solve my problem. Please go
ahead with your PR.
> MockProperty.setValue(final String[] newValues) throws null pointer exception
> ------------------------------------------------------------------------------
>
> Key: SLING-8066
> URL: https://issues.apache.org/jira/browse/SLING-8066
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing JCR Mock 1.4.0
> Reporter: Pankaj Parashar
> Assignee: Stefan Seifert
> Priority: Blocker
> Fix For: Testing JCR Mock 1.4.2
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> There is no null check in this api method. In our case product code is
> passing a null value in the below form for a multivalve property.
> currentNode.setProperty(propertyName, (String[])null);
> MockProperty api throws null pointer exception when we use JCR mocking.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
