jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-2068) null value could be set into propertyDefinition
Date Thu, 09 Apr 2009 14:11:12 GMT

    [ https://issues.apache.org/jira/browse/JCR-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697513#action_12697513
] 

Stefan Guggisberg commented on JCR-2068:
----------------------------------------

i agree with sergey. this is IMO a bug. passing a null value in setProperty is perfectly legal
according to the spec (setting a property to null is equivalent to calling the remove() method
on the property instance. it certainly shouldn't throw a runtime exception.

however, i wasn't able to reproduce it with a local jackrabbit instance.  might be a RMI related
issue. 

> 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: Improvement
>          Components: jackrabbit-core
>    Affects Versions: 1.5.3
>         Environment: Windows XP, Tomcat 6.0, JRE6
>            Reporter: Sergey Sachkov 
>         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