jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Buchmann (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JCR-1616) Spi2Dav / 283 Conflict: Creation of PropertyInfoImpl fails with NPE if the returned ItemInfo points to a Node
Date Wed, 07 Mar 2012 13:00:58 GMT

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

David Buchmann commented on JCR-1616:

additionally, the json returned for a node that has both a child and a property with the same
name is invalid:


there can't be twice the same key in a json object.
> Spi2Dav / 283 Conflict: Creation of PropertyInfoImpl fails with NPE if the returned ItemInfo
points to a Node
> -------------------------------------------------------------------------------------------------------------
>                 Key: JCR-1616
>                 URL: https://issues.apache.org/jira/browse/JCR-1616
>             Project: Jackrabbit Content Repository
>          Issue Type: Bug
>          Components: jackrabbit-jcr-server, jackrabbit-spi2dav
>    Affects Versions: 2.0, 2.1, 2.2, 2.3, 2.4
>            Reporter: angela
> jcr-server and jcr2spi do not deal properly with the following 283 functionality 
> - property and node siblings can have the same name
> this results in NPE upon creation of a PropertyInfoImpl from time to time:
> java.lang.NullPointerException
> 	at org.apache.jackrabbit.spi2dav.PropertyInfoImpl.<init>(PropertyInfoImpl.java:62)
> 	at org.apache.jackrabbit.spi2dav.RepositoryServiceImpl.getPropertyInfo(RepositoryServiceImpl.java:914)
> this issue cannot be fix by checking the value of the ItemResourceConstants.JCR_TYPE.
> instead a fix MUST include cover both jcr-server and jcr2spi and deal with the fact that
there are
> nodes/properties with the same name. consequently a different URI must be created for
> in order to have the server/client properly deal with the requests/responses.
> since there are currently no plans for upgrading SPI and spi2dav in particular to jcr
283 this issue
> acts as a reminder.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message