[
https://issues.apache.org/jira/browse/OAK-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485968#comment-13485968
]
Michael Dürig commented on OAK-395:
-----------------------------------
I think throwing a {{PathNotFoundException}} is the correct thing to do here.
However as it seems to create backward compatibility issues we need to decide
whether we either
# document this and fix the client code or,
# return a "PropertyImpl which throws ItemNotExistException on invocation of
any method on it".
I'd slightly prefer 1.
> Inconsistency in Node#setProperty in case of null value
> -------------------------------------------------------
>
> Key: OAK-395
> URL: https://issues.apache.org/jira/browse/OAK-395
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Reporter: angela
> Assignee: angela
>
> Setting a null value to a single valued property will result
> in 'null' being returned while executing the same on a multivalued
> property will return the removed property.
> jr2 returned the removed property in both cases as far as i
> remember and i would suggest that we don't change that behavior. in
> particular since the specification IMO doesn't allow to return
> null-values for these methods.
--
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
