Thanks Jukka, that fixed it. With the 1.4.1 patch and data store turned back on, should performance be better when persisting versioned files?
Jukka Zitting wrote: > > Hi, > > On Jan 30, 2008 4:36 PM, Jim_Cross <[EMAIL PROTECTED]> wrote: >> Has anyone else seen the following behaviour in Jackrabbit 1.4? >> >> A file exists in a given directory and is versioned. >> Check out the file >> Put a new version of the file >> Check the file in >> The content length now shows as 0 bytes, and getting the file returns a >> 0-byte file >> >> This seems to be caused by checking the file in - before that, a PROPFIND >> shows the correct content length, and a GET returns the file correctly. >> Diffing the two PROPFIND responses (before and after checkin) shows both >> have the same href, including version number, but different content >> lengths. > > This sounds similar to some of the other reports we've seen about > binary properties. As a workaround, try adding a > -Dorg.jackrabbit.useDataStore=false system property setting to your > server JVM. We are planning to publish a 1.4.1 patch release next week > with a fix to this issue. > > BR, > > Jukka Zitting > > -- View this message in context: http://www.nabble.com/WebDAV%3A-Checkin-on-versionsed-resource-results-in-0-byte-file-tp15183204p15224703.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
