Hi Peter, I did succeed in the setup you describe below. The problem, I guess, you encountered was that changing the version parameter directly in the database doesn't work, at least until a restart of your application. But after a restart of the application, the versioning of files will work. In your webfolder, you'll only see the newest version of the document but if you look in the FileContentStore, you'll see your file with different revision numbers like this: -rw-r--r-- 1 root root 48 Feb 11 22:55 test2.txt_1.0 -rw-r--r-- 1 root root 48 Feb 19 18:10 test2.txt_1.1 -rw-r--r-- 1 root root 75 Feb 19 18:13 test2.txt_1.2 -rw-r--r-- 1 root root 92 Feb 20 16:12 test2.txt_1.3
The next problem is, that there is no easy way to get old versions out of the system. What I did to get this into a functional system was to change in the Slide API to make setVersioned a public method and build a webinterface that allows me to enable versioning on an already uploaded file as well as download old versions of each file. Best regards, Jan ----- Original Message ----- From: "Nevermann, Dr., Peter" <[EMAIL PROTECTED]> To: "'Slide Users Mailing List'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, February 26, 2002 11:19 AM Subject: RE: version control > Hi Srinivas, > > as I told Cevat, what you would need are versioning-aware store > implementations for content and meta data to refer to in your domain > configuration (domain.xml). It also depends on *where* you are going to > store each kind of data (e.g. content data on the file system, meta data in > jdbc database). > > I am currently not aware of which of the existing implementation in the > "slidestore" package do support versioning. > > I tried myself with the following stores: > (a) slidestore.reference.FileContentStore for content (which aparently > supports versions) > (b) slidestore.reference.MemoryDescriptorsStore for metadata > (c) slidestore.file.XMLFileDescriptorsStore for metadata > > Unfortunately I did *not* get it work properly - SORRY! The problem is that > PUT still overwrites the last revision instead of creating a new one > (although the "version" parameter is set "true"). Maybe you can fix problems > in these store implementations yourself? > > My domain config contains: > > <store name="filesys"> > <contentstore classname="slidestore.reference.FileContentStore"> > <parameter name="version">true</parameter> > </contentstore> > <!--nodestore classname="slidestore.file.XMLFileDescriptorsStore" > /--> > <nodestore classname="slidestore.reference.MemoryDescriptorsStore" > /> > <securitystore> > <reference store="nodestore" /> > </securitystore> > <lockstore> > <reference store="nodestore" /> > </lockstore> > <revisiondescriptorstore> > <reference store="nodestore" /> > </revisiondescriptorstore> > <revisiondescriptorsstore> > <reference store="nodestore" /> > </revisiondescriptorsstore> > <parameter name="rootpath">C:\</parameter> > </store> > <scope store="filesys" match="/filesys" /> > > Regards, Peter > > > > -----Original Message----- > > From: Srinivas Rao [mailto:[EMAIL PROTECTED]] > > Sent: Monday, February 25, 2002 14:07 > > To: Slide Users List > > Subject: RE: version control > > > > > > Hi Peter & Cevat, > > > > I am also working on versioning of documents through Slide. My problem > > is, I am able to display the document details through Webdav server. > > when i click on any document link, it is opeining the document. I am > > able to store the document with updated content. Now the question is, > > whenever I save the document through the browser, i want to > > increase the > > version number and store the document with an appended > > version number in > > the system and update the "versions" table etc. for this, I > > have to call > > store() method of content object. Right? Webdav Servlet is calling > > various classes like GetMethod, PropFindMethod depending on the user > > actions. > > > > In which of the classes of Slide( I mean GetMethod, PutMethod,etc) I > > need to write this? > > > > Any idea on this?? > > > > regards > > Srinivas > > > > -----Original Message----- > > From: Nevermann, Dr., Peter [mailto:[EMAIL PROTECTED]] > > Sent: Friday, February 22, 2002 3:48 PM > > To: 'Slide Users List' > > Subject: RE: version control > > > > > > Cevat, > > > > > can anybody explain how to version control in slide? > > > thanks > > > > By which means (or interface) do you want to do versioning? > > > > (a) If it is through the Slide API, version control is primarily given > > through the "content helper" interface > > (org.apache.slide.content.Content). > > Other classes/interfaces which are crucial for versioning are: > > - org.apache.slide.content.NodeRevisionDescriptors > > - org.apache.slide.content.NodeRevisionNumber > > > > (b) If you mean through WebDAV, support for DeltaV (see > > http://webdav.org/deltav) is currently under construction in > > Slide, and > > will > > be available with the next version of Slide. > > > > Regards, > > - Peter. > > --------------------------------------- > > Dr. Peter Nevermann > > Software AG, Research & Development > > Uhlandstr. 12, 64292 Darmstadt, Germany > > +49-6151-92-1828 (phone), 92-1609 (fax) > > mailto:[EMAIL PROTECTED] > > http://www.softwareag.com > > > > > > > -----Original Message----- > > > From: Cevat Ikibas [mailto:[EMAIL PROTECTED]] > > > Sent: Thursday, February 21, 2002 22:28 > > > To: [EMAIL PROTECTED] > > > Subject: version control > > > > > > > > > > > > > > > can anybody explain how to version control in slide? > > > thanks > > > > > > cevat > > > > > > _________________________________________________________________ > > > MSN Photos is the easiest way to share and print your photos: > > > http://photos.msn.com/support/worldwide.aspx > > > > > > > > > -- > > > To unsubscribe, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > > <mailto:[EMAIL PROTECTED]> > > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > -- > > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
