You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-user@jakarta.apache.org by Unger Richard <ru...@camino.at> on 2002/09/02 17:43:03 UTC
Problems wih DAV:autoversion = DAV:checkout
Hi!
I just returned from holidays and am following this thread with interest. I
have been trying for quite some time to get versioning working with my
slide-setup, with no success. Some questions:
* Do I need a CVS version of slide to play with versioning, or will the
1.0.16 release do?
* Do I need to configure slide as a webapp within my own servlet container,
or will the default slide tomcat setup do?
* Do I need to use a certain database / store? I have tried Oracle and
postgresql, as well as file-stores, all without success...
* Do I need to use the slide-client to test? Is there a way I can get
versioning to happen using webfolders under windows2k (yes, Ugh, but in the
end it is what my customers will be using)?
* The auto-version parameter is missing from my domain.xml file... could
someone send me a sample domain.xml with this stuff in it?
In fact, if someone could send me a sample domain.xml and server.xml file
with which the versioning is working, and tell me which version of slide
they were using I think I could get it all going...
Richie
-----Ursprüngliche Nachricht-----
Von: Nevermann, Dr., Peter [mailto:Peter.Nevermann@softwareag.com]
Gesendet: Montag, 19. August 2002 12:18
An: 'Slide Users Mailing List'
Betreff: RE: Problems wih DAV:autoversion = DAV:checkout
Maybe not yet documented correctly:
The auto-version parameter in Domain.xml specifies the default value for the
DAV:auto-version property of resources which are newly set under version
control.
Regards,
Peter
> -----Original Message-----
> From: Thamm, Russell [mailto:russell.thamm@dsto.defence.gov.au]
> Sent: Monday, August 19, 2002 08:33
> To: 'Slide Users Mailing List'
> Subject: RE: Problems wih DAV:autoversion = DAV:checkout
>
>
> Hi Peter,
>
> I'm using a version of Slide that I downloaded last Monday
> (the lastest
> nightly build).
>
> I set up slide as outlined Thomas Scheuppel.
>
> PUT /slide/files/test.txt => Created V1
>
> Changed "auto-version-control" to "false" in domain.xml.
>
> PUT /slide/files/aaa.txt => No new version
> VERSION-CONTROL /slide/files/aaa.txt => Created V1
> PUT /slide/files/aaa.txt => Created V2
>
> Changed "auto-version" to "checkout" in domain.xml.
>
> PUT /slide/files/aaa.txt => Created V3
>
> However, I have now looked at the DAV:auto-version property of
> aaa.txt and see that it is "checkout-checkin" and changing
> this property in domain.xml didn't change this property
> for existing files <silly me :-)>
>
>
> thanks
> Russell
>
>
> -----Original Message-----
> From: Nevermann, Dr., Peter [mailto:Peter.Nevermann@softwareag.com]
> Sent: Thursday, August 15, 2002 6:17 PM
> To: 'Slide Users Mailing List'
> Subject: RE: Problems wih DAV:autoversion = DAV:checkout
>
>
> Hi Russel,
>
> I could not reproduce your problem with the latest nightly build.
>
> Which version of SLIDE did you use?
> What exactly is your scenario? How did you set DAV:auto-version to
> DAV:checkout?
> Could is be misspelling of the property name (DAV:autoversion
> instead of
> DAV:auto-version)?
>
>
> Roughly, what I did is the following:
>
> - PUT /slide/files/a.xml
> - VERSION-CONTROL /slide/files/a.xml
> - PROPPATCH /slide/files/a.xml (DAV:auto-version = DAV:checkout
>
> VERSION-CONTROL creates a history at /slide/history/1 and a
> 1st version
> /slide/history/1/1.0. Due to DAV:auto-version =
> DAV:checkout-checkin, the
> PROPPATCH creates a 2nd version /slide/history/1/1.1. My
> scenario continues:
>
> - PUT /slide/files/a.xml
> - PROPFIND /slide/files/a.xml (requesting DAV:checked-out and
> DAV:checked-in)
> - PROPFIND /slide/history/1 (Depth: 1)
>
> Both PROPFINDs show me that the resource is checked-out and
> that no new
> version has been created.
>
> Regards, Peter
>
>
> > -----Original Message-----
> > From: Thamm, Russell [mailto:russell.thamm@dsto.defence.gov.au]
> > Sent: Thursday, August 15, 2002 08:33
> > To: Slide Users Mailing List
> > Subject: Problems wih DAV:autoversion = DAV:checkout
> >
> >
> > Hi,
> >
> > I have been playing with the DELTAV stuff in Slide.
> >
> > Everything seems to work pretty much as expected. But when I set
> > autoversion to checkout, Slide does not behave as I expect.
> >
> > According to my understanding, if I PUT a new copy of a checked-in
> > version-controlled
> > resource, the old copy should be checked out, the new copy
> > should overwrite
> > the
> > checked-out resource, but no checkin should occur and no new
> > version should
> > be created until I perform an explicit checkin.
> >
> > However, when I do this, Slide creates a new version, exactly as if
> > autoversion were set to checkout-checkin.
> >
> > Am I misunderstanding this?
> >
> > thanks
> > Russell Thamm
> >
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>