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]>
