From users-return-4927-apmail-jackrabbit-users-archive=jackrabbit.apache.org@jackrabbit.apache.org Thu Sep 13 08:12:13 2007 Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 55967 invoked from network); 13 Sep 2007 08:12:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Sep 2007 08:12:11 -0000 Received: (qmail 32409 invoked by uid 500); 13 Sep 2007 08:12:04 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 32178 invoked by uid 500); 13 Sep 2007 08:12:03 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 32169 invoked by uid 99); 13 Sep 2007 08:12:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2007 01:12:03 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [194.8.61.8] (HELO spamslammer2.tirol.gv.at) (194.8.61.8) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Sep 2007 08:12:01 +0000 Received: from mailscan1.tirol.local (mailscan1.tirol.local [10.10.128.204]) by spamslammer2.tirol.gv.at (Spamslammer) with ESMTP id 181F951CU6 for ; Thu, 13 Sep 2007 10:11:38 +0200 (CEST) Received: from mxs0.tirol.local (unverified) by mailscan1.tirol.local (Clearswift SMTPRS 5.2.9) with ESMTP id for ; Thu, 13 Sep 2007 10:11:38 +0200 Received: from mxs01.tirol.local ([10.10.128.211]) by mxs0.tirol.local with Microsoft SMTPSVC(6.0.3790.1830); Thu, 13 Sep 2007 10:11:38 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: AW: lock question Date: Thu, 13 Sep 2007 10:11:39 +0200 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: lock question Thread-Index: Acf1Pfdln44RjbjrScGwWifuY6/GfQAAZ6SgACdYltA= References: <90a8d1c00709120520m7a54067cube70eb2732832355@mail.gmail.com> <46E7DAF4.5040704@apache.org> <90a8d1c00709120532r1b9d5906u4850df87bc6e3347@mail.gmail.com> <90a8d1c00709120607h4892412dnb0dcb5d8dd1c1500@mail.gmail.com> From: =?iso-8859-1?Q?K=D6LL_Claus?= To: X-OriginalArrivalTime: 13 Sep 2007 08:11:38.0375 (UTC) FILETIME=[B56D1170:01C7F5DD] X-Virus-Checked: Checked by ClamAV on apache.org can anybody help me with this scenario ? i have read the specification and i see no solution to myproblem. if the webdav impl creates a non sessionscoped lock=20 -> DAVResourceImpl.lock(LockInfo) on a node and then do not remove it (only if the normal worklow is = interrupted) i have a node in the repository that can not be unlocked .. greets claus -----Urspr=FCngliche Nachricht----- Von: K=D6LL Claus [mailto:C.KOELL@TIROL.GV.AT]=20 Gesendet: Mittwoch, 12. September 2007 15:47 An: users@jackrabbit.apache.org Betreff: AW: lock question i get the lock problems with the webdav servlet in some rarely situations like a user quits the ms word by the = taskmanager the webdav servlet can not release the lock from the node and so i have a node with a lock and i can not remove it=20 what can i do ? claus -----Urspr=FCngliche Nachricht----- Von: Stefan Guggisberg [mailto:stefan.guggisberg@gmail.com]=20 Gesendet: Mittwoch, 12. September 2007 15:08 An: users@jackrabbit.apache.org Betreff: Re: lock question On 9/12/07, K=D6LL Claus wrote: > hi stefan, > > first thanks for the infos. > how can i remove the lock if i can not save the lock token from the = first session. > > something like this .. > > session.getRootNode().getNode("path/to/lockable/node").lock(true, = false); > now log out .. > login again and remove the lock .. how ? you need to retrieve the lock token *before* the session logs out, e.g. by calling Lock lock =3D ....lock(true, false); String token =3D lock.getLockToken(); or // about to log out... String[] tokens =3D session.getLockTokens(); > > thanks > claus > > -----Urspr=FCngliche Nachricht----- > Von: Stefan Guggisberg [mailto:stefan.guggisberg@gmail.com] > Gesendet: Mittwoch, 12. September 2007 14:33 > An: users@jackrabbit.apache.org > Betreff: Re: lock question > > On 9/12/07, Carsten Ziegeler wrote: > > Stefan Guggisberg wrote: > > > you need to transfer the lock token from the session that created = the > > > lock to the new session., e.g. like this: > > > > > > Lock lock =3D > > > > > > sessionA.getRootNode().getNode("path/to/lockable/node").lock(true, > > > false); > > > String token =3D lock.getLockToken(); > > > sessionA.removeLockToken(token); > > > ... > > > sessionB.addLockToken(token); > > > = sessionB.getRootNode().getNode("path/to/lockable/node").unlock(); > > > > > > > > Is it required to remove the lock token from the first session? > > if you log out the first session before you transfer the lock token, = no. > otherwise you'll have to remove it since only one session can hold > a particular lock token. > > cheers > stefan > > > > > Carsten > > > > -- > > Carsten Ziegeler > > cziegeler@apache.org > > >