Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 4137 invoked from network); 28 Dec 2003 15:06:53 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 28 Dec 2003 15:06:53 -0000 Received: (qmail 77343 invoked by uid 500); 28 Dec 2003 15:06:47 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 77314 invoked by uid 500); 28 Dec 2003 15:06:47 -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 77301 invoked from network); 28 Dec 2003 15:06:47 -0000 Received: from unknown (HELO mx0.rambler.ru) (81.19.66.47) by daedalus.apache.org with SMTP; 28 Dec 2003 15:06:47 -0000 Received: from mailc.rambler.ru (mailc.rambler.ru [81.19.66.27]) by mx0.rambler.ru (Postfix) with ESMTP id 8D123433819 for ; Sun, 28 Dec 2003 18:06:48 +0300 (MSK) (envelope-from on@ukr.net) Received: from localhost.localdomain ([213.130.8.206]) (authenticated bits=0) by mailc.rambler.ru (8.12.10/8.12.10) with ESMTP id hBSF4jXM026641 for ; Sun, 28 Dec 2003 18:04:48 +0300 (MSK) Content-Type: text/plain; charset="iso-8859-1" From: Oleg Nitz Reply-To: on@ukr.net To: "OJB Developers List" Subject: Re: [PFE] locking via database for multi-VM environment Date: Sun, 28 Dec 2003 17:10:23 +0000 User-Agent: KMail/1.4.2 References: <200312201740.33853.on@ukr.net> <200312252319.52324.on@ukr.net> <3FEB722E.2040606@code-au-lait.de> In-Reply-To: <3FEB722E.2040606@code-au-lait.de> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200312281710.23350.on@ukr.net> X-Auth-User: nitz, whoson: (null) 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 Armin, On Thursday 25 December 2003 23:26, Armin Waibel wrote: > This code will definitely work in non-managed environment. If you using > a managed environment (e.g. j2ee conform appServer, Tomcat+JTA) per > default all created connection/DataSource are associated with the > running transaction. When using these connections it's not allowed to > change autoCommit state and it's not allowed to do commit or rollback. > So, if you ask OJB for a new PB instance with a new connection this > connection will be normally associated with the running tx (in most > cases you will get different connections handles of the same connection= ). > > Thus we need a separate connection-descriptor with > - an ordinary direct jdbc connection to DB (or to inMemory DB) > or > - an DataSource configurated not to be automatic associated with tx > > Shouldn't be problem ;-) Thanks for your explanation, I agree. > hmm, in our feature list we say "Distributed Lockmanagement", but > current persistent lock manager does not work. From that point of view > it's important. But I don't know if it is possible to implement your > proposed lock manager before 1.0, because time is short! > What do you think? I think it would be better just to remove "Distributed Lockmanagement" fr= om=20 the feature list. I can't promise that I will do this in a short time lim= it,=20 sorry.=20 --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org