[
https://issues.apache.org/jira/browse/JCR-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12520468
]
André Bierwolf commented on JCR-1053:
-------------------------------------
Thanks for fixing this issue. I agree with the solution of returning null here,
because I already check for null when adding a element.
I don't initialize my collection until the first add.
> Calling size method of a ManageableArrayList causes NullPointerException
> ------------------------------------------------------------------------
>
> Key: JCR-1053
> URL: https://issues.apache.org/jira/browse/JCR-1053
> Project: Jackrabbit
> Issue Type: Bug
> Components: jcr-mapping
> Affects Versions: 1.3
> Reporter: André Bierwolf
> Assignee: Christophe Lombart
> Attachments: NTCollectionConverterImpl.diff
>
>
> When using the NTCollectionConverterImpl with proxy="true" a call on the size
> () method of a ManageableArrayList causes a NullPointerException if there is
> no underlying List. LazyCollectionLoader doLoad returns null because there is
> are no children.
> The ManageableArrayList is created because the isNull method of the
> NTCollectionConverterImpl class always returns false.
> According to the comment line this is done because the getCollectionNodes
> always returns a list.
> But after the fix for JCR-882 this is not correct anymore.
> The attached fix corrects this.
> The only question remaining is how to differ between an empty list and a
> null-value for the field containing the list.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
