hi
so some batch job releasing the given locks at startup of the repository
server would be ok.
thx for your help
dietmar
Angela Schreiber schrieb:
hi
if i'm not mistaken JCR-441 deals with session-scoped locks,
that must be released whenever the lock-holding session
is logged out.
however, the simple-dav-servlet does create open-scoped
locks. during normal workflow Word unlocks the resource as soon
as a user has finish editing the document by closing it.
but you are right, if you shut down the server that lock
will not be released. this is a general issue with
open-scoped locks: if you loose the lock-token there is
no reasonable way to remove the lock.
i don't think that its the job of the webdav-servlet to
guess if an open-scoped lock should be released or not.
this is rather an 'administrator' task to make sure, that
such abandoned locks can be removed again.
regards
angela
I'm editing rtf documents via Word and the SimpleWebdavServlet. The
data is kept in an Oracle instance. Everything works fine except you
shut down the server while a user is editing a document. The lock the
user has on the node isn't released - so after a restart of the
server the document can't be modified anymore.
Usually the session should unlock the node when released. I think [
http://issues.apache.org/jira/browse/JCR-441?page=all ] deals with
the same problem and is fixed in the latest version 2.2.2. I tried it
with the latter but the problem still exists.
any idea
thx
Dietmar
