Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
2.0, 2.1, 2.2, 2.3, 2.4
-
None
-
None
Description
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 them
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.
Attachments
Issue Links
- depends upon
-
JCR-2005 JCR2SPI: Remove validation check for same-named Node and Property
- Closed