Jackrabbit 1.4 and Problems with Failed Document Uploads

For those who prefer to live and bleed on the cutting edge of things, you must have already started experimenting with Jackrabbit 1.4 that came out in Janurary, 2008.

Well then most of you must have alse encountered a problem with uploading documents that worked perfectly with previous versions but fails. The upload succeeds, but unless the repository is manually restarted, attempts to access the newly uploaded document throws an exception with the following stack trace :

javax.jcr.RepositoryException: Internal error while retrieving value of /SecondTest/nb/field/*Value3*: name can't be null: name can't be null at org.apache.jackrabbit.core.PropertyImpl.getValue(PropertyImpl.java:470) at org.apache.jackrabbit.core.PropertyImpl.getStream(PropertyImpl.java:479) at com.sun.portal.cms.mirage.service.custom.impl.ContentServiceImpl.getFieldValue(ContentServiceImpl.java:677) at com.sun.portal.cms.mirage.service.custom.impl.ContentServiceImpl.getContentFromNode(ContentServiceImpl.java:393) at com.sun.portal.cms.mirage.service.custom.impl.ContentServiceImpl.getContentByNameAndType(ContentServiceImpl.java:351) at com.sun.portal.cms.mirage.service.custom.impl.ContentServiceImpl.getContentsByType(ContentServiceImpl.java:434) at com.sun.portal.cms.portlet.ccd.beans.ContentCreationBean.changeContentType(ContentCreationBean.java:220)

Caused by: java.lang.NullPointerException: name can't be null
 at java.io.FilePermission.init(FilePermission.java:171)
 at java.io.FilePermission.(FilePermission.java:264)
 at java.lang.SecurityManager.checkRead(SecurityManager.java:871)
 at java.io.FileInputStream.(FileInputStream.java:100)

at org.apache.jackrabbit.core.value.BLOBInTempFile.getStream(BLOBInTempFile.java:145) at org.apache.jackrabbit.core.value.InternalValue.toJCRValue(InternalValue.java:366) at org.apache.jackrabbit.core.PropertyImpl.getValue(PropertyImpl.java:466)

      ... 97 more
java.lang.NullPointerException: name can't be null

Well thanks to the following my problem is at least temporarily solved:
http://www.mail-archive.com/users@jackrabbit.apache.org/msg06191.html

A better understanding of the problem is called for so that I can address it more appropriately in the future.
But for now setting the system property org.jackrabbit.useDataStore to false fixes it immediately.