maxwell at umiacs.umd.edu wrote: > Last year, in a thread entitled "Subversion and XXE", we discussed > autoversioning when XXE saved files to a WebDav server. Your comment, > Hussein, was: > >> Some of our customers use XXE with apache+mod_dav+mod_dav_svn as a >> back end ... >> When DeltaV is properly configured: >> - You lock the file >> (in the case of XXE, this happens automatically when you open a >> document), >> - You modify the locked file and save it as many times as you want. >> - A new version is automatically created when you *unlock* the file >> (in the case of XXE, this happens automatically when you close the >> document being edited). >> >> This behavior seems fine and intuitive. >> >> XXE should work fine when used as a naive WebDAV DeltaV client. >> If this is not the case, consider this as bug. We really want XXE to >> behave correctly when used with a WebDAV DeltaV backend. > > We now have WebDav and Subversion set up, and we cannot get this behavior > to work. Specifically, if autoversioning is set to ON,
Configuring autoversioning is more complicated that just turning it ON. You'll want to configure autoversioning to a mode called: DAV:checkout-unlocked-checkin. See http://www.webdav.org/specs/rfc3253.html#rfc.section.2.2.2 > we get a new > version with every save; if we set it to OFF, we can't save at all, > instead we get an error: > Cannot save document "https://svn....": > Conflict [409] > I get the same results for both the ON and the OFF setting with Exclusive, > Shared and None locking set in XMLmind's options for remote filesystems. > > This is with XMLMind v3.7.1 (we'll be upgrading to 3.8.1 next week, but I > don't see anything in the changes listing that would indicate the XXE > WebDav client changed). The WebDav plugin in XMLmind reports version > 1.01. Java SE runtime is 1.6.0_06. We are using version > 2.2.3-11.el5_1.centos.3.x86_64 of Apache, with mod_dav_svn version > 1.4.2-2.el5.x86_64, and SubVersion 1.4.2-2.el5.x86_64. (I notice that's a > bit old.) > > There are a few things we can play around with here, one of which is to > try a newer mod_dav_svn / SubVersion. Do you have any other suggestions? > Do you have a mod_dav_svn server set up somewhere, and perhaps the > configuration file(s) for that server? There aren't any settings in XXE > that would affect how the WebDav client works, are there? (apart from the > Shared/Exclusive/None locking setting) > A couple of years ago, we have thoroughly tested XXE against mod_dav_svn / SubVersion and it worked fine. We cannot retest it in the short term because: [1] After upgrading the test machine, we didn't take the time to reinstall mod_dav_svn / SubVersion. [2] We are currently [a] extremely busy releasing XXE v4 and [b] moving our offices to another location! (XXE v4 uses the same WebDAV client but with an http.jar where some bugs have been fixed: I can send you this patched http.jar if you want.) Everything in what you said suggests that mod_dav_svn / SubVersion is not properly configured. I suggest to test your installation with another WebDAV client such as Cadaver (http://www.webdav.org/cadaver/). Make sure not to use any versioning feature: just plain lock/put/put/put/.../unlock. I guess that you'll have exactly the same problems. Sorry not to be able to help you more.
