Hi Thomas,
> 1. When I use the struts-example.jsp on a
> versioned resource, there are some values
> that I don't understand:
> # hasRevisions: true; # isVersioned: false
> whats the difference between the two?
I think that normally each NodeRevisionDescriptors (NRDS) instance has the
1.0 revision and therefore hasRevisions() should normally return true. The
isVersioned() method returns the value of the useVersioning flag of the
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.
> There is one Revision 1.0 and 0.0 in the list,
> although the property checked-in holds
> <D:href xmlns:D="DAV:">/history/3/1.3</D:href>
> I would have expected all Versions 1.0, 1.1,
> 1.2, 1.3 to be in the list. What am I
> getting wrong?
Because the revisions are stored at the VHR, not at the VCR. This is forced
by the DeltaV architecture.
> 2. Using HTTP, how do I get the latest revision
> number of a resource? I.E. "1.3" for the above
> example. Is that only possible by requesting a
> REPORT and parsing the full results?
Hhmmm ... it is not very comfortable in DeltaV to pick out the latest
revision from a history, I fear. Probably using the "version-tree" report is
the best way to do it.
Regards, Peter
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
