Newbee: Understanding question WebDAV-Protocoll

Hello Miguel,

thanks, this hint helps me very much. Now it is all a little
bit clear to
me. So I have downloaded the client api and tried to send
data from the
pdm-system to the centera and also from the pdm-system to a
simple
filesystem - it works all very fine and like expected.
So now I can try to test all required functions to step more
and more into
the webdav world. And if I have any further questions, I
know, where I find
competent help 

Thank you very much.

Regards
Mario 


Miguel Figueiredo wrote:
> 
> Hello Mario,
> 
>  You dont need Slide Server to use ECM Centera, just
the slide client API.
> It is available from jackarta downloads site, at
> http://jakarta.apache.org/site/downloads/downloads_s
lide.cgi ->
> 2.1_client.zip (for example). Then it's all about using
the containing jar
> (or source if u prefer) on your eclipse pdm-system
project.
> 
> If you like, it would be great to test the webdav
client API against the
> Centera server, just to see webdav protocol working.
> 
>  Best Regards,
>  Miguel Figueiredo
> 

-- 
View this message in context: http://www.nabbl
e.com/Newbee%3A-Understanding-question-WebDAV-Protocoll-tf41
02995.html#a11805990
Sent from the Jakarta Slide - User mailing list archive at
Nabble.com.


------------------------------------------------------------
---------
To unsubscribe, e-mail: slide-user-unsubscribejakarta.apache.org
For additional commands, e-mail: slide-user-helpjakarta.apache.org

Hi Miguel,

I was wandering into this list and read this thread in
whole. 
A very brief introduction: I am using Webdav to
programatically (Java) bulk
import text files from local drive into EMC eRoom Server.
This line explains
all my environment. I am using Slide client library. 

Can you help me in this specific question: By default the
lastModified time
of imported file is the current time when it is imported.
Can I override
this behaviour and retain the original time from source
location.

The 'WebdavFile' class has no such method. But
'WebdavResource' has a method
setGetLastModified but it is protected. I think if I extend
it in my custom
class I can achieve this. 

Any comments on this.

-- 
View this message in context: http://www.nabbl
e.com/Newbee%3A-Understanding-question-WebDAV-Protocoll-tf41
02995.html#a12663741
Sent from the Jakarta Slide - User mailing list archive at
Nabble.com.


------------------------------------------------------------
---------
To unsubscribe, e-mail: slide-user-unsubscribejakarta.apache.org
For additional commands, e-mail: slide-user-helpjakarta.apache.org

Hello mate,

 If you need to do change the lastModified time of a
resource, I would
consider that an hacker wish ;)
 No way you're going to be able to that, especially if you
are using the
client API. You would need to change server behavior, and in
a way that the
server would not follow webdav specification directives. The
reason is
pretty straightforward: webdav specification states that
resources have
"live" and "dead" properties, being the
dead properties the ones we can
PROPPATCH, that is, we can create, update and remove them
from the resource.
The live properties values, like lastModified, creationDate,
contentLength,
contentType, are calculated in real time (maybe stored
afterwards) with
server information. For that reason, they are protected, and
can't be
changed by the user (I'll just copy paste and excerpt from
rfc4918):
"
   Live Property - A property whose semantics and syntax are
enforced by
   the server.  For example, the live property
DAV:getcontentlength has
   its value, the length of the entity returned by a GET
request,
   automatically calculated by the server.
"

 I believe that the protected method setGetLastModified
purpose is to set
the date value on the local image of a remote resource. So
overriding won't
help you on your intention.

 I don't know why you must change lastModified value, but if
it is a
business decision, I would suggest you to create a new
property for storing
the value that you want (ex: <insert your namespace
here>:getLastModified).

Hope this helps,
Miguel Figueiredo

-----Original Message-----
From: pk_jsp [mailto:pkrishnamgmmirage.com] 
Sent: quinta-feira, 13 de Setembro de 2007 22:16
To: slide-userjakarta.apache.org
Subject: RE: Newbee: Understanding question
WebDAV-Protocoll


Hi Miguel,

I was wandering into this list and read this thread in
whole. 
A very brief introduction: I am using Webdav to
programatically (Java) bulk
import text files from local drive into EMC eRoom Server.
This line explains
all my environment. I am using Slide client library. 

Can you help me in this specific question: By default the
lastModified time
of imported file is the current time when it is imported.
Can I override
this behaviour and retain the original time from source
location.

The 'WebdavFile' class has no such method. But
'WebdavResource' has a method
setGetLastModified but it is protected. I think if I extend
it in my custom
class I can achieve this. 

Any comments on this.

-- 
View this message in context:
http://www.nabble.com/Newbee%3A-Unde
rstanding-question-WebDAV-Protocoll-tf41
02995.html#a12663741
Sent from the Jakarta Slide - User mailing list archive at
Nabble.com.


------------------------------------------------------------
---------
To unsubscribe, e-mail: slide-user-unsubscribejakarta.apache.org
For additional commands, e-mail: slide-user-helpjakarta.apache.org


------------------------------------------------------------
---------
To unsubscribe, e-mail: slide-user-unsubscribejakarta.apache.org
For additional commands, e-mail: slide-user-helpjakarta.apache.org

Miguel Figueiredo wrote:
> Hello mate,
> 
>  If you need to do change the lastModified time of a
resource, I would
> consider that an hacker wish ;)
>  No way you're going to be able to that, especially if
you are using the
> client API. You would need to change server behavior,
and in a way that the
> server would not follow webdav specification
directives. The reason is
> pretty straightforward: webdav specification states
that resources have
> "live" and "dead" properties, being
the dead properties the ones we can
> PROPPATCH, that is, we can create, update and remove
them from the resource.
> The live properties values, like lastModified,
creationDate, contentLength,
> contentType, are calculated in real time (maybe stored
afterwards) with
> server information. For that reason, they are
protected, and can't be
> changed by the user (I'll just copy paste and excerpt
from rfc4918):
> "
>    Live Property - A property whose semantics and
syntax are enforced by
>    the server.  For example, the live property
DAV:getcontentlength has
>    its value, the length of the entity returned by a
GET request,
>    automatically calculated by the server.
> "
> ...

Well.

This means that a server is *allowed* to reject a request
setting 
DAV:getlastmodified. But it doesn't have to.

Best regards, Julian

------------------------------------------------------------
---------
To unsubscribe, e-mail: slide-user-unsubscribejakarta.apache.org
For additional commands, e-mail: slide-user-helpjakarta.apache.org