Hello Stefan,
Thanks for your contribution the other time
I tried the code snippet but I get only the latest revision.
For instance I had revisions 1.0,1.1,1.2
It brings out only 1.2 as the lis of revision numbers available for that resource.
What is it that is the problem
Pls I will appreciate your reply today.
Thanks in advance
Gbenga
Stefan Fromm <[EMAIL PROTECTED]> wrote:
Hello Gbenga,
1) I want to able to view the list of all previous revision number
[revision history] for a specific document resource thru the Java
application. Which class of the slide native api helps to achieve
this. I have searched the api doc but couldn't get something
meaningful yet. Pls I need your input
Note that there might occur problems with the versions because functionality
is implemented inconsistently in the helper-layer and WebDAV-layer as mentioned
in these messages:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg06761.html
http://www.mail-archive.com/[EMAIL PROTECTED]/msg03708.html
http://www.mail-archive.com/[EMAIL PROTECTED]/msg10230.html
So it depends on if you access versions with Slide-API or via WebDAV.
For Slide-API it should work like this:
NamespaceAccessToken nsat =
Domain.accessNamespace(new SecurityToken(""), Domain.getDefaultNamespace());
SlideToken token = new SlideTokenImpl(new CredentialsToken(slideusername));
Content contentHelper = nsat.getContentHelper();
NodeRevisionDescriptors revisions = contentHelper.retrieve(token, "/files/test.txt");
for ( Enumeration e = revisions.enumerateRevisionNumbers(); e.hasMoreElements(); )
{
NodeRevisionNumber nrno = (NodeRevisionNumber)e.nextElement();
// get metadata
NodeRevisionDescriptor nrd = contentHelper.retrieve(token, revisions, nrno);
// get content
NodeRevisionContent nrc = contentHelper.retrieve(token, revisions, nrd);
}
For WebDAV there is defined the DAV:version-tree report in RFC3253
(DeltaV Specification). See http://www.ietf.org/rfc.html
2) I want to be able to request to view content for a specific
revision (from the revision history) of a document . Take for
instance, if there are the following revision nos for a document
resource; 1.0,1.1,1.2,1.3,1.4 where 1.4 is the latest document
revision number. I should be able to programmatically and randomly
pool revision 1.2 to see what is in there.
NodeRevisionNumber provides some constructors where you can provide a
version number in different ways. In connection with the above shown
code for Helper-API you should be able to do it.
For WebDAV it could be the additional Label-Header in the GET-request
where you can provide a version label. Since version numbers are just
server-side generated version labels this could work.
3) You may have observed the way slide handles numbering of revisions
for a document; that instead of increamenting the whole number part of
the revision no, it rather increaments the decimal part of the number.
Take for instance, if previous revision number is 1.0. When Slide does
the next revision, it assigns the number, 1.1
At what point will it move the version numbering to 2.0?
To me it seems there is never created a next major version. Good points
to have a look at are
org.apache.slide.content.ContentImpl and
org.apache.slide.webdav.util.VersioningHelper
Regards
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
