Every PROPPATCH creates a new version provided that the auto-version parameter is set to checkout-checkin.
Make sure you have both parameters, auto-version and auto-version-control, set to the same value when comparing stores. If you don't want a PROPPATCH to create a new version you have to switch to another versioning scheme such as checkout and require an explicit checkin whenever there is a need for a new version. Ingo > I am trying to add a document(content) to the JDBC store with some custom properties. > If a new revision is created when doing a proppatchMethod call - then > the code below would create multiple revisions. Is this correct behaviour for > proppatch or do the > proppatch calls only get "committed" when calling versionControlMethod()? > > However this is not happening in the file store and only one version is created. > I could be doing something wrong so will go back and check. > > I used the DAVExplorer to check version history and saw only one revision > when using a File store and multiple revisions when using a JDBC store. > > Michael > > -----Original Message----- > From: Oliver Zeigermann [mailto:[EMAIL PROTECTED] > Sent: 19 October 2004 11:39 > To: Slide Users Mailing List > Subject: Re: auto-versioning diff between JDBC and File store > > > Not quite sure. One thing I can say is properties get versioned as well, > so it makes sense to create a new revision descriptor for every > proppatch. I am wondering: aren't properties being versioned in the file > store??? I thought they were... Or are you talking about content? > Slightly confused... > > Oliver > > Michael Gluckman schrieb: > > > Hi > > I am putting a resource under version control using the following code snippet: > > Auto-versioning is turned on. > > > > boolean success = res.putMethod(path, content); > > if (!success) { > > throw new DocumentException(res.getStatusMessage()); > > } > > success = res.proppatchMethod(path, new PropertyName(NAMESPACE, > > RESOURCE_ID_PROPERTY_NAME), Integer.toString(newId), true); > > if (!success) { > > throw new DocumentException(res.getStatusMessage()); > > } > > success = res.proppatchMethod(path, new PropertyName(NAMESPACE, > > RESOURCE_TYPE_PROPERTY_NAME), type, true); > > if (!success) { > > throw new DocumentException(res.getStatusMessage()); > > } > > > > success = res.versionControlMethod(path); > > > > When I do this using a file index store, then only 1 version is created (which is > > what I want). > > If I try this using a JDBC store then I get multiple revisions created for every > > proppatchMethod. Is this the correct behaviour for > > proppachMethod() ? > > > > Regards > > Michael --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
