Angela Schreiber wrote:
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?
you mean in terms of jcr? no.... not that i would
know of. the semantics of javax.jcr.lock.Lock.getToken()
will change slightly with jsr283 (regarding session-scoped
locks) but for with jsr 170 its defined to be:
"If this <code>Session</code> holds the lock token for this lock,
then this method will return that lock token. If this
<code>Session</code> does not hold the applicable lock
token then this method will return null."
Right, I forgot that. Sorry.
> ...
BR, Julian
