Angela Schreiber wrote:
hi roland
as far as i know, the <locktoken> element is present
in the lock-discovery property if the jcr-session
that has been attached to the request is the lock-holder.
Hm, is that a voluntary restriction in the WebDAV layer? What is it for?
otherwise it's omitted. this is mainly due to the nature
of the the JCR-Lock that is created by default:
the JCR Lock object only reveals the lock token if the
Session that obtained the lock from the node is the
lock-holder.
Isn't that incorrect for open-scoped locks?
...
BR, Julian