hello Martin,

you said one of the parameters should be

> <parameter name="auto-version-control">true</parameter>

but I have got the feeling that it turns on auto-versioning, which gives the following behaviour: each time I do a PUT on a resource which already exists, the version number is incremented...no need for VERSIONCONTROL nor CHECKOUT nor CHECKIN, or am I wrong?

If I am, how do I get that behaviour in Slide?

thanks,

Stan.

Martin Holz wrote:
eric scroger <[EMAIL PROTECTED]> writes:


I've got Slide installed and configured under Tomcat 4.1.18.
I've got nodestore set up to save in our Postgresql database.
I've got the contentstore set up to use the filesystem.
I have been using the Slide client to perform WebDAV
transactions.

How do I go about using versioning with the transfer of
files under WebDAV using slide?  I looked at the nodestore
table, revisions, and I see all the uri's have their isversioned
column set to 0.  I tried setting one record's isversioned column
to 1, but I still haven't gotten versioning to work.  Thanks in
advance.


First make a backup of postgres and file system.

Then you have to make a few changes in Domain.xml
Change the version parameter in  FileContentStore
to true. At the same time you must rename all
files. On a unix system you can do something like

find $SLIDEDATA/files -type f -exec mv {} {}_1.0 \;

Change the parameters at the end of Domain.xml to

<parameter name="historypath">/history</parameter>
<parameter name="workspacepath">/workspace</parameter>
<parameter name="workingresourcepath">/workingresource</parameter>
<parameter name="auto-version">checkout</parameter>
<parameter name="auto-version-control">true</parameter>
<parameter name="checkout-fork">forbidden</parameter>
<parameter name="checkin-fork">forbidden</parameter>


I added this to the end of my data section, but I am not sure,
if it is necessary to give anybody all rights on /history

     <objectnode classname="org.apache.slide.structure.SubjectNode" uri="/history" >
            <permission action="/actions" subject="/users" />
     </objectnode>
     <objectnode classname="org.apache.slide.structure.SubjectNode" uri="/workspace"/>
     <objectnode classname="org.apache.slide.structure.SubjectNode" 
uri="/workingresource"/>

If you start the webdav servlet now, versioning should work.
To a acually put the files under version control, you must make a
VERSION-CONTROL request on the resource. In cadaver you could use the version command to do so. A ^ is shown in cadaver directory listing in front of all version-controlled resources.



And don't forget the backup.


Martin

--
Martin Holz     <[EMAIL PROTECTED]>

Softwareentwicklung / Vernetztes Studium - Chemie
FIZ CHEMIE Berlin
Franklinstrasse 11
D-10587 Berlin



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to