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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2014/08/15 13:45:18 UTC

[jira] [Resolved] (OAK-2026) Incompatibility with PropertyDefinitionImpl#getValueConstraints potentially returning null values.

     [ https://issues.apache.org/jira/browse/OAK-2026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig resolved OAK-2026.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1
         Assignee: Michael Dürig

Thanks Amit for the patch. Applied at http://svn.apache.org/r1618158

> Incompatibility with PropertyDefinitionImpl#getValueConstraints potentially returning null values.
> --------------------------------------------------------------------------------------------------
>
>                 Key: OAK-2026
>                 URL: https://issues.apache.org/jira/browse/OAK-2026
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Amit Jain
>            Assignee: Michael Dürig
>            Priority: Minor
>             Fix For: 1.1
>
>         Attachments: OAK-2026.patch
>
>
> There is an compatibility issue with the {{org.apache.jackrabbit.oak.plugins.nodetype.PropertyDefinitionImpl#getValueConstraints}} where it returns null if not available. 
> In  {{org.apache.jackrabbit.webdav.jcr.nodetype.PropertyDefinitionImpl#toXml}} call in the component {{jackrabbit-jcr-server}}, it assumes that {{#getValueConstraints}} would not return null, which used to work with Jackrabbit 2.x. But with Oak’s {{org.apache.jackrabbit.oak.plugins.nodetype.AbstractTypeDefinition}}, where the above call is delegated it can return null.



--
This message was sent by Atlassian JIRA
(v6.2#6252)