Hi Lionel,

I'll try your suggestion in the WebDAV servlet's putMethod class,
.../webdav/server/org/apache/slide/webdav/method/PutMethod.java
(I was looking in webDAV client 
.../webdav/client/src/org/apache/webdav/lib/methods/PutMethod.java)

With any luck I can get the webdav servlet to do versioning.
I'll post the results.

thanks for your help and patience.
Anton


-----Original Message-----
From: Lionel Touati [mailto:[EMAIL PROTECTED]]
Sent: Tue 02 July 2002 13:51
To: Slide Users Mailing List
Subject: RE: Versioning


My Comments below

-----Message d'origine-----
De :
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
.org]De la part de Anton Schoultz
Envoy� : Tuesday, July 02, 2002 1:42 PM
� : 'Slide Users Mailing List'
Objet : RE: Versioning


Hi Lionel,

So if I understand correctly, you have an application which runs
with the server and communicates via the SLIDE API.
(and versioning works fine)

True

If this is the case, then it seems that slide's core (&api) supports
versioning, but perhaps the code in the WebDAV servlet is not up to
date with the versioning yet? IOW the servlet code may need to be
updated to make use of the versioning offered in the SLIDE API ?

I'd guess so, and what is quite good is that if a node is versionned, then
instead of
updating the node, it'll create a new revision.


BTW had a look at the client's putMethod - nothing much there :) -
it simply extends the HTTP put method, with no particular changes
that I could see.


At the end of the executeRequest method, you'll find

   content.create(slideToken, resourcePath, revisionDescriptor,
                               revisionContent);

This bits creates a new node, but it's not versionned,

If you prepend this statement with
content.create(userToken, uri, true);

Then all the nodes you'll create will be versionned. I'm working on 1_0_16
which might be different from yours

L.




Thanks for the input
Anton

-----Original Message-----
From: Lionel Touati [mailto:[EMAIL PROTECTED]]
Sent: Tue 02 July 2002 13:32
To: Slide Users Mailing List
Subject: RE: Versioning


Hi Anton,

Yes I use versionning but not via the WebDav API. What I know is that the
PutMethod doesn't create the versionning support for the node, but if I
update a file that has versionning support, then it works. That's why I
pointed out this

L.


-----Message d'origine-----
De :
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
.org]De la part de Anton Schoultz
Envoy� : Tuesday, July 02, 2002 1:06 PM
� : 'Slide Users Mailing List'
Objet : RE: Versioning


Hi Lionel,

I'll have a look into the putMethod class to see if it gives me any ideas.

As I understand it, versioning is configured in the slide server (not
client).

I have played with variations of the suggestion made by Peter Neverman
(2002/05/14)
which configured the content store (in Domain.xml) as

        <contentstore classname="slidestore.reference.FileContentStore">
          <parameter name="rootpath">contentstore</parameter>
          <!-- ........... versioning is ON ..................... -->
          <parameter name="version">true</parameter>
          <!-- ........... keep content data after restart ...... -->
          <parameter name="resetBeforeStarting">false</parameter>
        </contentstore>

Following Thomas Schueppel's suggestion (2002/06/26) [he had problems with
versioning on filecontentstore - but worked with hsql store]

I have tried using a JDBC (hsql) based content store too, with file and JDBC
type node stores, all in vain. I can overwrite the stored document, but the
version
is not updated. Trying to place a file under version control (using client's
versioncontrol command) returns an error. I believe that the settings in
domain.xml

        <auto-version>checkout-checkin</auto-version>

mean that all files are automatically under version control,
and that they should get a new version number each time that the file is
over-written into the store.

The command line-tool does not support checkin nor checkout (as listed by
the help text). I am trying to wrap the client side by utilizing the
WebdavResource class, but invoking the
webdavResource.versionControlMethod(sHostDir)
didn't help either. I'm running out of ideas here.

Does anyone have versioning working? If so, please let me know what your
configuration
looks like (esp. domain.xml) Perhaps Thomas Schueppel could share how he got
versioning
working on his system ? :)

Many thanks
Anton

-----Original Message-----
From: Lionel Touati [mailto:[EMAIL PROTECTED]]
Sent: Tue 02 July 2002 12:40
To: Slide Users Mailing List
Subject: RE: Versioning


Hi Anton,

>From my experience files created using the webdav client are not versionned
by default. That's
why you probably can't get any version history in it. You should probably
dig into PutMethod.java to see what's going on

L.


-----Message d'origine-----
De :
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
.org]De la part de Anton Schoultz
Envoy� : Monday, July 01, 2002 1:31 PM
� : SLIDE User Group (E-mail)
Objet : Versioning


Hi,

I'm trying to get verify versioning but can't seem to get it right.
I'm using SLIDE as on 2002-06-20 in Tomcat on Win2000.
I have versioning turned on in Domain.xml.
I have tried with FileStore and with jdbc store (hsql) but have
not been able to get a list of version history. How would I
request an older version of a file using the webdav client?
If anyone has got versioning going, I'd appreciate it if you
could drop me a line with some pointers, a sort of HOW-TO.

Many Thanks

Anton Schoultz

Rubico (Pty) Ltd
Cell Phone:  +27 83 651 7191
Tel:  +27 (11) 808 1000
Fax:  +27 (11) 808 1101
[EMAIL PROTECTED]
www.Rubico.com

The Business Component Company

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

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to