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 2013/05/13 15:03:15 UTC

[jira] [Commented] (OAK-815) Wrong type for empty multi-valued property

    [ https://issues.apache.org/jira/browse/OAK-815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13655942#comment-13655942 ] 

Marcel Reutegger commented on OAK-815:
--------------------------------------

The underlying problem is the way how Oak stores a multi-valued property without a value. The empty array does not hold type information. When the type is later requested {{PropertyImpl}} simply falls back to a default STRING type.
                
> Wrong type for empty multi-valued property
> ------------------------------------------
>
>                 Key: OAK-815
>                 URL: https://issues.apache.org/jira/browse/OAK-815
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core, jcr
>    Affects Versions: 0.7
>            Reporter: Marcel Reutegger
>
> While implementing JCR versioning in Oak I noticed that the type for a multi-valued property with an empty array returns the wrong type. E.g. this happens when a node is checked in and the jcr:predecessors property is set to an empty array. Property.getType() then says it's of type STRING, while in fact it should say it's of type REFERENCE.

--
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