Thanks again Ingo I have yet another versioning question. I would really appreciate if you could please answer the following:
The behavior that you have described below(i.e. multiple put and proppatch after checkout without creating multiple versions) is part of the checkout-in-place feature. Right? Is there any way to overwrite the content/properties of a particular version without creating a new version? As I understand, WebdavResource provides an "updateMethod" which copies the content from one version to another. However my requirement is different, I just want to overwrite the last version without creating a new version. Basically I want to have the version tree but also give the user an option to overwrite the last version. I think I can achieve this by doing a checkout-put-checkin and then overwriting the contents of the previous version with that of the newly created version and finally deleting the newly created version (not sure whether deleting versions is supported). However even if this route is possible, it is very cumbersome. Secondly, I tried updating/adding property values to a particular version but got an error "cannot-modify-version". Is it possible to modify the properties of an earlier version without forking/versioning? Regards, Ritu -----Original Message----- From: Ingo Brunberg [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 8:56 PM To: [EMAIL PROTECTED] Subject: Re: Adding Labels to Resource Versions A CHECKIN does exactly what you cited: It effectively creates a new version as a copy (content and properties) of the version controlled resource. To create a new version with different content than the currently checked-in version controlled resource you first have to check-out the VCR, than modify it with PUT and/or PROPPATCH and finally do a CHECKIN. The previous version is not affected by this procedure. Ingo > Thanks Ingo > > The labeling did work on the version href. > > I have another versioning question: The checkin method does not take data > input-stream/bytes. Ideally I expected that a checkin would take the revised > content from the client for creating the new version. > > I saw the DeltaV specs: > > CHECKIN Method (applied to a version-controlled resource) > > A CHECKIN request can be applied to a checked-out version-controlled > resource to produce a new version whose content and dead properties > are copied from the checked-out resource. > > The above comment suggests that the same content as the previous checked-out > version will be copied into the new version. > Given this, Slide is doing the right thing. But I did not understand the > rationale behind this. Shouldn't a "put" be implicit as part of a Checkin? > > Given the way it works, does it mean that for checking in a new version I > will have to do an explicit put for the version URI just created by the > "checkin" method? > > Thanks and Regards, > Ritu --------------------------------------------------------------------- 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]
