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 "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2012/10/30 15:40:12 UTC
[jira] [Reopened] (OAK-395) Inconsistency in Node#setProperty in
case of null value
[ https://issues.apache.org/jira/browse/OAK-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcel Reutegger reopened OAK-395:
----------------------------------
Assignee: Marcel Reutegger (was: angela)
I'll prepare a patch...
> 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: Marcel Reutegger
>
> 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