Thanks for you help, Thomas!
I was wondering what kind of behavior in regards to versioning can one
expect when using a simple client such as WebDrive. As far as I can see,
WebDrive only does GET/PUT/PROPPATCH operations. I am not locking or
checking in/out files. I understand that there is some implicit
checkout/checkin going on... I am seeing a lot of exceptions when doing
GET/PUT operations:
org.apache.slide.content.RevisionAlreadyExistException: Revision 1.1 already
exists on object /history/1
at
slidestore.reference.FileContentStore.createRevisionContent(FileContentStore
.java:294)
at
org.apache.slide.store.AbstractStore.createRevisionContent(AbstractStore.jav
a:1225)
at
org.apache.slide.store.StandardStore.createRevisionContent(StandardStore.jav
a:654)
at org.apache.slide.content.ContentImpl.create(ContentImpl.java:528)
at
org.apache.slide.webdav.util.VersioningHelper.checkin(VersioningHelper.java:
1151)
at
org.apache.slide.webdav.method.PutMethod.executeRequest(PutMethod.java:274)
...
and
org.apache.slide.content.RevisionDescriptorNotFoundException: No revision
descriptor found on object /history/2
at
slidestore.j2ee.J2EEDescriptorsStore.retrieveRevisionDescriptor(J2EEDescript
orsStore.java:1161)
at
org.apache.slide.store.StandardStore.retrieveRevisionDescriptor(StandardStor
e.java:561)
at
org.apache.slide.content.ContentImpl.retrieve(ContentImpl.java:291)
at
org.apache.slide.webdav.util.VersioningHelper.checkin(VersioningHelper.java:
1124)
at
org.apache.slide.webdav.method.PutMethod.executeRequest(PutMethod.java:274)
...
Usually, after retrying the operation succeeds. I can't predictably
re-create these situations, they just seem to happen at random. I am also
getting the following exception when I PUT new versions of the first file
that I create in the respoitory:
org.apache.slide.webdav.util.PreconditionViolationException: Forbidden
at
org.apache.slide.webdav.util.VersioningHelper.checkout(VersioningHelper.java
:775)
at
org.apache.slide.webdav.method.PutMethod.executeRequest(PutMethod.java:222)
at
org.apache.slide.webdav.method.AbstractWebdavMethod.run(AbstractWebdavMethod
.java:323)
at
org.apache.slide.webdav.WebdavServlet.service(WebdavServlet.java:221)
...
I understand that this is caused by the file already being checked out. But
when I create additional files, this no longer happens: I can save new
versions without problems.
Thanks
Andrei
-----Original Message-----
From: Thomas Schueppel [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 10, 2002 9:07 AM
To: Slide Users Mailing List
Subject: Re: Versioning
Solodin, Andrei wrote:
> Hi, I also have followed Thomas Schueppel's instructions to get versioning
> working. But I am seeing some unexpected results. I am using J2EE store
for
> descriptors and file system store for content. Odd things I am seeing:
>
> 1) When I save new versions of a document, I see that the name of the
actual
> file in my contentstore file dir remains at _1.0, while versions created
> under history are directories named 1, 2, 3 etc. Each directory contains
> files named 1.0, 1.1 etc. Just by looking at listing under /history,
there's
> no way of knowing which document a particular version belongs to.
This is the normal behaviour. You can find out which History
belongs to which Resource by evaluating the values returned
by a version-history REPORT-Request. (See DeltaV Documentation).
Slide client 'REPORT <uri> x' seems to do this.
The client crashes if you leave away the x although it's not
necessary(?).
> 2) I noticed that when creating new content, RevisionDescriptors object is
> still created with isVersioned = false. Is this normal?
Yes this is normal. I'm quoting Peter Nevermann here:
"The isVersioned() method returns the value of the useVersioning flag of
the NodeRevisionDescriptors (NRDS).
In the context of DeltaV, only NRDS of version history resources (VHR,
e.g. /slide/history/1) are versioned. A VHR always has the 0.0 revision
to store the metadata of the VHR itself ("version-history" branch), and
revisions 1.0, 2.0, ... for the versions in the history. A version
resource (VR) is represented in Slide only by its structure aspect (i.e.
has no NRDS), as its metadata is contained in the correponding history.
Finally, the NRDS of a version controlled resource (VCR) is not
versioned and contains always the 1.0 revision and sometimes a 0.0
revision ("backup" branch), e.g. when the VCR is checked-out."
l8r...
Thomas
--
Thomas Sch�ppel, bit~side GmbH Fon: +49+30+394054-28
Salzufer 14a, 10587 Berlin Fax: +49+30+394054-50
http://www.bit-side.com Email: [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]>
