Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 30332 invoked from network); 17 Jan 2004 17:10:35 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 17 Jan 2004 17:10:35 -0000 Received: (qmail 58080 invoked by uid 500); 17 Jan 2004 17:10:27 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 58055 invoked by uid 500); 17 Jan 2004 17:10:27 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 58039 invoked from network); 17 Jan 2004 17:10:27 -0000 Received: from unknown (HELO smtp.web.de) (217.72.192.208) by daedalus.apache.org with SMTP; 17 Jan 2004 17:10:27 -0000 Received: from p50902241.dip.t-dialin.net ([80.144.34.65] helo=web.de) by smtp.web.de with asmtp (TLSv1:RC4-MD5:128) (WEB.DE 4.99 #566) id 1Ahtxu-00023P-00 for ojb-dev@db.apache.org; Sat, 17 Jan 2004 18:10:30 +0100 Message-ID: <40096BDA.50102@web.de> Date: Sat, 17 Jan 2004 18:07:38 +0100 From: Thomas Mahler Reply-To: thma@apache.org Organization: Apache Foundation User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030821 X-Accept-Language: en-us, en MIME-Version: 1.0 To: OJB Developers List Subject: ODMG distributed LockManagement X-Enigmail-Version: 0.76.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: thma32@web.de X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N hi all, I've just checked in my solution for the buggy PersistentLockMapImpl. It's called RemoteLockMapImpl. Now all Odmg clients that use this map store their lock in a LockServer implemented as a servlet. This servlet is the singleton entry point for all lock requests. Everything is configured through OJB.properties. There is also some short explanation there. But I'll check in some more documentation later. There is a new ant target lockservlet-war that assembles the ready to deploy war file. It has been tested with Tomcat 4.1.27 and all Junit tests pass. Implementing this beast was quite a bulk of work, but I'm happy that we can ship 1.0 without a known major issue! have a nice weekend, Thomas --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org