Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
Message-ID: <002d01c6713d$5f549400$0300a8c0@tyohuone>
From: "Mikko Peltonen" <mikko.peltonen@netikka.fi>
To: <users@jackrabbit.apache.org>
Subject: Node (un)locking in transaction
Date: Sat, 6 May 2006 21:46:23 +0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit

Hi All,

I'm having problems to get Node.unlock() to work under a different session 
and transaction from the session/transaction under which the Node was 
locked. I've been trying to transfer the lock token between 
transactions/sessions but Node.unlock() always throws LockException "Node 
not locked by this session" in XAEnvironment's unlock method.

Looking into the source of XAEnvironment, the addLockToken() method's 
implementation is empty:
/**
 * Add lock token to this environment.
 * @param lt lock token
 */
public void addLockToken(String lt) {
}

And if I understood correctly after a quick look into the source, 
Session.addLockToken() gets delegated to this method when we are under 
transaction. Am I missing something here, or doesn't addLockToken work under 
transactions? Can I lock a node under transaction/session A and then unlock 
it under transaction/session B and how?

Regards,
Mikko