Hi Paco, You have to remove the lock token from the other session first. The specification, section 8.4.8, says:
"Note that since at most one session per repository may hold the same lock token, serial access to the locked item is ensured." Adding a lock token already owned by session A to some other session B prints a warning message in jackrabbit, in accordance to the specification of JSR170 1.0, while in 1.0.1 it will throw a LockException. Regards Dominique On 11/5/06, Paco Avila <[EMAIL PROTECTED]> wrote:
I need to unlock a node locked by another session, but when I add the lock token to the session and perfom an unlock and exception is thrown: Node not locked by session. JCR-170 specification says that any session can unlock a node if the lock token is added to the session (8.4.6). -- Paco Avila <[EMAIL PROTECTED]>
