Roland Porath wrote:
All the webdav clients I've looked at so far seem to default to an infinite lock depth even if the resource is not a collection.
Lock depth infinity simply is the default, and from WebDAV's point of view, for non-collection resources the semantics are exactly the same. So there's really no reason not to stick with the default.
Jackrabbit does not seem to like that and is not able to remove the lock. Now the question: is that a bug or a feature. It does not make a lot of sense to have an infinite lock depth on a non collection so jackrabbit would be justified to whinge. On the other hand the clients (and slide webdav server) seem to have a different opinion.
As Angela said: more information required. Does the LOCK request fail? If it didn't, what does PROPFIND on DAV:lockdiscovery reveal?
BR, Julian
