We have implemented the bug workaround that you suggested earlier, namely starting XXE (pro edition) with the following parameter -putpref lockTimeout 0 added to the command line. This was to work around the bug where XXE couldn't save a changed file back to an SVN (WebDAV) server. We only use the above parameter once on each machine, after that it seems to automagically work.
However, we now have a different bug: sometimes (unpredictably), after someone shuts down XXE, the SVN server thinks they still have their files locked. I then have to go in on the command line and type "svn unlock --force..." to break the lock before anyone (including the original user) can edit the file. We're still on XXE v5.1.1; our IT department doesn't like to re-install things without persuasion. Is there a fix for this bug? Or has anyone even reported it? I don't know how to reliably reproduce it--seems to only happen sometimes (possibly the user immediately logs out of Windows after closing XXE, and the setting doesn't propogate??? but computers are generally faster than we are :-)). Mike Maxwell University of Maryland -- XMLmind XML Editor Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xmleditor-support
