You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Padraic Hannon (JIRA)" <ji...@apache.org> on 2007/07/31 04:00:53 UTC
[jira] Created: (JCR-1044) NTCollectionConverterImpl throws a null
pointer exception on update
NTCollectionConverterImpl throws a null pointer exception on update
-------------------------------------------------------------------
Key: JCR-1044
URL: https://issues.apache.org/jira/browse/JCR-1044
Project: Jackrabbit
Issue Type: Bug
Components: jcr-mapping
Affects Versions: 1.3
Environment: All
Reporter: Padraic Hannon
When calling update on a node which has no child nodes stored (but which can have child nodes) the code can generate a null pointer exception. In the case where one goes to remove JCR nodes which are not present in the current objects collection of child objects the code is calling getCollectionNodes().iterator(). However, since is not checking for the case where getCollectionNodes() returns null if there are no child nodes present a null pointer exception will be generated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (JCR-1044) NTCollectionConverterImpl throws a null
pointer exception on update
Posted by "Padraic Hannon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Padraic Hannon updated JCR-1044:
--------------------------------
Attachment: NTCollectionConverterImpl.diff
This puts a null check around the code which is attempting to delete JCR nodes not present in the current objects collection.
> NTCollectionConverterImpl throws a null pointer exception on update
> -------------------------------------------------------------------
>
> Key: JCR-1044
> URL: https://issues.apache.org/jira/browse/JCR-1044
> Project: Jackrabbit
> Issue Type: Bug
> Components: jcr-mapping
> Affects Versions: 1.3
> Environment: All
> Reporter: Padraic Hannon
> Attachments: NTCollectionConverterImpl.diff
>
>
> When calling update on a node which has no child nodes stored (but which can have child nodes) the code can generate a null pointer exception. In the case where one goes to remove JCR nodes which are not present in the current objects collection of child objects the code is calling getCollectionNodes().iterator(). However, since is not checking for the case where getCollectionNodes() returns null if there are no child nodes present a null pointer exception will be generated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (JCR-1044) NTCollectionConverterImpl throws a null
pointer exception on update
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christophe Lombart reassigned JCR-1044:
---------------------------------------
Assignee: Christophe Lombart
> NTCollectionConverterImpl throws a null pointer exception on update
> -------------------------------------------------------------------
>
> Key: JCR-1044
> URL: https://issues.apache.org/jira/browse/JCR-1044
> Project: Jackrabbit
> Issue Type: Bug
> Components: jcr-mapping
> Affects Versions: 1.3
> Environment: All
> Reporter: Padraic Hannon
> Assignee: Christophe Lombart
> Attachments: NTCollectionConverterImpl.diff
>
>
> When calling update on a node which has no child nodes stored (but which can have child nodes) the code can generate a null pointer exception. In the case where one goes to remove JCR nodes which are not present in the current objects collection of child objects the code is calling getCollectionNodes().iterator(). However, since is not checking for the case where getCollectionNodes() returns null if there are no child nodes present a null pointer exception will be generated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (JCR-1044) NTCollectionConverterImpl throws a null
pointer exception on update
Posted by "Christophe Lombart (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JCR-1044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christophe Lombart resolved JCR-1044.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.4
Patch applied - Thanks
> NTCollectionConverterImpl throws a null pointer exception on update
> -------------------------------------------------------------------
>
> Key: JCR-1044
> URL: https://issues.apache.org/jira/browse/JCR-1044
> Project: Jackrabbit
> Issue Type: Bug
> Components: jcr-mapping
> Affects Versions: 1.3
> Environment: All
> Reporter: Padraic Hannon
> Assignee: Christophe Lombart
> Fix For: 1.4
>
> Attachments: NTCollectionConverterImpl.diff
>
>
> When calling update on a node which has no child nodes stored (but which can have child nodes) the code can generate a null pointer exception. In the case where one goes to remove JCR nodes which are not present in the current objects collection of child objects the code is calling getCollectionNodes().iterator(). However, since is not checking for the case where getCollectionNodes() returns null if there are no child nodes present a null pointer exception will be generated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.