You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-user@jakarta.apache.org by Rolf Kulemann <ro...@apache.org> on 2004/04/09 09:56:27 UTC
Locking a resource and act on it in a different (WebDAV) session
Is it "normal" behaviour, that I can not i.e. update a locked resource
as the same user, which locked the resource, if I try to update the
resource in a different session in which the lock was created?
To reproduce it (Using a webdav client):
- login as user A -> session x
- "lock files/norace.xml"
- login again as user A -> session y
- session y: put src.xml norace.xml -> Status 423 (locked?)
I ask only to make sure if this is "a defined WebDAV behaviour". Reading
the WebDAV spec. I could not find the answer. Or is this behaviour slide
specific?
--
Regards,
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: Slide2rc1 webdav weird behaviour
Posted by Julian Reschke <ju...@gmx.de>.
Peder Nordvaller wrote:
> Hello, I just setup Slide 2 rc 1 and I experience a small bug(?) with the
> webdav servlet... When creating a new folder IE creates a folder named "New
> Folder". I then rename it and it works just fine. But when I refresh the IE
> window the name "New Folder" reappears instead of the new name.
>
> Doing a trace with Ethereal of the PROPFIND gives me for example:
> ...
> <D:response xmlns:D="DAV:">
> <D:href>/fsserver/bla</D:href>
> <D:propstat>
> <D:prop>
> <D:creationdate>2004-04-09T16:05:05Z</D:creationdate>
> <D:getlastmodified>Fri, 09 Apr 2004 16:05:05
> GMT</D:getlastmodified>
> <D:getcontentlength>0</D:getcontentlength>
> <D:displayname>New Folder (3)</D:displayname>
> <D:resourcetype>
> <D:collection />
> </D:resourcetype>
> </D:prop>
> <D:status>HTTP/1.1 200 OK</D:status>
> </D:propstat>
> <D:propstat>
> <D:prop>
> <D:name />
> <D:parentname />
> <D:href />
> <D:ishidden />
> <D:isreadonly />
> <D:getcontenttype />
> <D:contentclass />
> <D:getcontentlanguage />
> <D:lastaccessed />
> <D:iscollection />
> <D:isstructureddocument />
> <D:defaultdocument />
> <D:isroot />
> </D:prop>
> <D:status>HTTP/1.1 404 Not Found</D:status>
> </D:propstat>
> </D:response>
> ...
>
> The displayname property does not update correctly when renaming (MOVE:ing)
> the folder. Same thing with files (non-collections nodes). Is there
> something I have set up wrong or is this something that needs to be fixed?
> It could easily be added in the MoveMethod if so but might want to be done
> in the Macro?
Hi, there are several bugs involved here, but MOVE not changing the
displayname is absolutely correct.
Bug #1: it seems that somebody is silently letting default the
DAV:displayname property to the last path segment when a folder is
created. Automatically setting DAV:displayname to be identical to the
last part of the URL doesn't make any sense at all. In absence of the
DAV:displayname property, any client will display the last URL segment
anyway. So this seems to be a bug in Slide's MKCOL (and possibly other
methods that create new resources such as PUT or COPY).
Note: Apache/moddav works exactly as it should: DAV:displayname only
appears when it's explicitly set using PROPPATCH; namespace operations
do not affect DAV:displayname at all. On the other hand, in Microsoft
IIS DAV:displayname is a computed property that's always equal to the
last path segment (minus escaping), meaning it's not settable at all. I
consider this a bug.
Bug #2: there are Microsoft webfolder versions that display
DAV:displayname *instead* of the last path segment (instead of *in
addition*). This issue is documented here:
<http://greenbytes.de/tech/webdav/webfolder-client-list.html#issue-displayname-1>,
and it would be nice if everybody would help pushing Microsoft to fix this.
Hope this helps,
Julian
--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Slide2rc1 users and groups
Posted by Peder Nordvaller <pe...@vitaminapplications.se>.
Is there any documentation regarding how to, via the Slide API, create
users, groups and permissions for these in Slide2? I'm coming directly from
1.0.16 where one created GroupNodes and UserRoleImpl objects but that seems
to be far from how it works today? Thankful for any pointers to docs,
snippets of code, or a brief explanation!
Regards, Peder Nordvaller
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Slide2rc1 webdav weird behaviour
Posted by Peder Nordvaller <pe...@vitaminapplications.se>.
Hello, I just setup Slide 2 rc 1 and I experience a small bug(?) with the
webdav servlet... When creating a new folder IE creates a folder named "New
Folder". I then rename it and it works just fine. But when I refresh the IE
window the name "New Folder" reappears instead of the new name.
Doing a trace with Ethereal of the PROPFIND gives me for example:
...
<D:response xmlns:D="DAV:">
<D:href>/fsserver/bla</D:href>
<D:propstat>
<D:prop>
<D:creationdate>2004-04-09T16:05:05Z</D:creationdate>
<D:getlastmodified>Fri, 09 Apr 2004 16:05:05
GMT</D:getlastmodified>
<D:getcontentlength>0</D:getcontentlength>
<D:displayname>New Folder (3)</D:displayname>
<D:resourcetype>
<D:collection />
</D:resourcetype>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
<D:propstat>
<D:prop>
<D:name />
<D:parentname />
<D:href />
<D:ishidden />
<D:isreadonly />
<D:getcontenttype />
<D:contentclass />
<D:getcontentlanguage />
<D:lastaccessed />
<D:iscollection />
<D:isstructureddocument />
<D:defaultdocument />
<D:isroot />
</D:prop>
<D:status>HTTP/1.1 404 Not Found</D:status>
</D:propstat>
</D:response>
...
The displayname property does not update correctly when renaming (MOVE:ing)
the folder. Same thing with files (non-collections nodes). Is there
something I have set up wrong or is this something that needs to be fixed?
It could easily be added in the MoveMethod if so but might want to be done
in the Macro?
Regards, Peder Nordvaller
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: Locking a resource and act on it in a different (WebDAV) session
Posted by Andreas Probst <an...@gmx.net>.
Hi Rolf,
I didn't know this, but I suppose this does exactly what I
meant. Normally you must use the same instance of
WebdavResource. This new method just steals the lock of another
instance.
Andreas
On 10 Apr 2004 at 15:15, Rolf Kulemann wrote:
> On Fri, 2004-04-09 at 23:12, Andreas Probst wrote:
> > Hi Rolf,
> >
> > to act on a locked resource it is necessary to give the lock
> > token in the request. If I remember correctly, the spec
> > recommends a client to send the lock token only if this client
> > issued the lock. This way no client can steal the lock of
> > another client of the same user. If you want to act on the
> > resource with another client, read the lock token and send it
> > with the request. So it should be possible the steal the lock of
> > the other session.
>
> Thanks, but my problem was solved with rc1. There is now a new method on
> the WebdavResource called discoverOwnLocks() which makes live much
> easier.
>
> Thanks for ur reply.
>
> --
> Regards,
>
> Rolf Kulemann
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
RE: Locking a resource and act on it in a different (WebDAV)session
Posted by Andreas Probst <an...@gmx.net>.
This is called stealing a thread, not stealing a lock.
On 10 Apr 2004 at 18:50, Uma Gajendragadkar wrote:
> Where can I download "rc1" from?
>
> Thanks
> Uma
>
> -----Original Message-----
> From: Rolf Kulemann [mailto:roku@apache.org]
> Sent: Saturday, April 10, 2004 6:46 PM
> To: Slide Users Mailing List
> Subject: Re: Locking a resource and act on it in a different
> (WebDAV)session
>
> On Fri, 2004-04-09 at 23:12, Andreas Probst wrote:
> > Hi Rolf,
> >
> > to act on a locked resource it is necessary to give the lock
> > token in the request. If I remember correctly, the spec
> > recommends a client to send the lock token only if this client
> > issued the lock. This way no client can steal the lock of
> > another client of the same user. If you want to act on the
> > resource with another client, read the lock token and send it
> > with the request. So it should be possible the steal the lock of
> > the other session.
>
> Thanks, but my problem was solved with rc1. There is now a new method on
> the WebdavResource called discoverOwnLocks() which makes live much
> easier.
>
> Thanks for ur reply.
>
> --
> Regards,
>
> Rolf Kulemann
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: slide-user-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
RE: Locking a resource and act on it in a different (WebDAV)session
Posted by Uma Gajendragadkar <um...@shakambhari.com>.
Where can I download "rc1" from?
Thanks
Uma
-----Original Message-----
From: Rolf Kulemann [mailto:roku@apache.org]
Sent: Saturday, April 10, 2004 6:46 PM
To: Slide Users Mailing List
Subject: Re: Locking a resource and act on it in a different
(WebDAV)session
On Fri, 2004-04-09 at 23:12, Andreas Probst wrote:
> Hi Rolf,
>
> to act on a locked resource it is necessary to give the lock
> token in the request. If I remember correctly, the spec
> recommends a client to send the lock token only if this client
> issued the lock. This way no client can steal the lock of
> another client of the same user. If you want to act on the
> resource with another client, read the lock token and send it
> with the request. So it should be possible the steal the lock of
> the other session.
Thanks, but my problem was solved with rc1. There is now a new method on
the WebdavResource called discoverOwnLocks() which makes live much
easier.
Thanks for ur reply.
--
Regards,
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: Locking a resource and act on it in a different (WebDAV)
session
Posted by Rolf Kulemann <ro...@apache.org>.
On Fri, 2004-04-09 at 23:12, Andreas Probst wrote:
> Hi Rolf,
>
> to act on a locked resource it is necessary to give the lock
> token in the request. If I remember correctly, the spec
> recommends a client to send the lock token only if this client
> issued the lock. This way no client can steal the lock of
> another client of the same user. If you want to act on the
> resource with another client, read the lock token and send it
> with the request. So it should be possible the steal the lock of
> the other session.
Thanks, but my problem was solved with rc1. There is now a new method on
the WebdavResource called discoverOwnLocks() which makes live much
easier.
Thanks for ur reply.
--
Regards,
Rolf Kulemann
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org
Re: Locking a resource and act on it in a different (WebDAV) session
Posted by Andreas Probst <an...@gmx.net>.
Hi Rolf,
to act on a locked resource it is necessary to give the lock
token in the request. If I remember correctly, the spec
recommends a client to send the lock token only if this client
issued the lock. This way no client can steal the lock of
another client of the same user. If you want to act on the
resource with another client, read the lock token and send it
with the request. So it should be possible the steal the lock of
the other session.
Regards,
Andreas
On 9 Apr 2004 at 9:56, Rolf Kulemann wrote:
> Is it "normal" behaviour, that I can not i.e. update a locked resource
> as the same user, which locked the resource, if I try to update the
> resource in a different session in which the lock was created?
>
> To reproduce it (Using a webdav client):
>
> - login as user A -> session x
> - "lock files/norace.xml"
> - login again as user A -> session y
> - session y: put src.xml norace.xml -> Status 423 (locked?)
>
> I ask only to make sure if this is "a defined WebDAV behaviour". Reading
> the WebDAV spec. I could not find the answer. Or is this behaviour slide
> specific?
>
>
> --
> Regards,
>
> Rolf Kulemann
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: slide-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: slide-user-help@jakarta.apache.org