jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (JCR-2068) null value could be set into propertyDefinition
Date Thu, 09 Apr 2009 15:57:13 GMT

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

Jukka Zitting resolved JCR-2068.
--------------------------------

    Resolution: Duplicate
      Assignee: Jukka Zitting

OK, thanks. Resolving as a duplicate of JCRRMI-17.

> null value could be set into propertyDefinition
> -----------------------------------------------
>
>                 Key: JCR-2068
>                 URL: https://issues.apache.org/jira/browse/JCR-2068
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr-rmi
>    Affects Versions: 1.5.3
>         Environment: Windows XP, Tomcat 6.0, JRE6
>            Reporter: Sergey Sachkov 
>            Assignee: Jukka Zitting
>            Priority: Minor
>         Attachments: JackRabbitTest.java, test.xml
>
>
> It is possible to set null value into propertyDefinition and NullPointer is thrown inside
JackRabbit in EffectiveNodeType class, checkSetPropertyValueConstraintsmethod  line 615. So
it would be good to check those values for null, as null pointer inside framwork is not a
good practice

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message