var propPatch = new PropPatchMethod(filePath);
propPatch.addPropertyToSet("auto-version", "<D:checkout/>", null, "DAV:");
var state = client.executeMethod(propPatch);Tim
James Mason wrote on 17/11/04 02:00 AM:
Tim,
I believe the behavior you're seeing is expected. There was a discussion about this a few weeks back, you may be able to find it in the archive. I don't know a lot about versions (maybe someone else can step in here), but as far as I know the auto-version parameter only effects newly-created resources. To change the behavior on existing resource you need to set a property on them directly (I don't know which property this is, but it sounds like you do ;) ). Try playing with propatch and propget and see if you can change the behavior.
-James
On Mon, 2004-11-15 at 12:54 -0500, Tim Frank wrote:
I have been trying to experiment with the various settings for auto-version specified in section 3.2.2 of the DeltaV RFC. I am either not understanding one of these options, or it is not operating as it should.
I have set the auto-version parameter to "checkout" in Domain.xml like this:
<parameter name="auto-version">checkout</parameter>
I am using the KDE webadv:// protocol and Windows Web Folders as my dumb clients, DAV Explorer as my smart client.
If I create a new file with DAV Explorer then the behaviour works as expected, the dumb clients only put the file in the checkout state, then I must use the smart client to check it in when complete.
However, if I try to use a file in the repository from before the configuration change, the old auto-version behaviour persists. Is this auto-version behaviour tied to every single file as it is created?? I can't seem to get any information on the auto-version property using a DASL search, it is always listed in the 404 response section. Is there a way to change the auto-version behaviour on a previously created resource?
Tim
--------------------------------------------------------------------- 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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
