Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 2785 invoked from network); 17 Nov 2006 17:14:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Nov 2006 17:14:21 -0000 Received: (qmail 46572 invoked by uid 500); 17 Nov 2006 17:14:29 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 46563 invoked by uid 500); 17 Nov 2006 17:14:29 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 46552 invoked by uid 99); 17 Nov 2006 17:14:29 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Nov 2006 09:14:29 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=SPF_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of clamey@localmatters.com designates 216.241.189.144 as permitted sender) Received: from [216.241.189.144] (HELO mailhost01.ad.corp.localmatters.com) (216.241.189.144) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Nov 2006 09:14:16 -0800 Received: from 10.4.0.152 ([10.4.0.152]) by mailhost01.ad.corp.localmatters.com ([10.200.4.32]) with Microsoft Exchange Server HTTP-DAV ; Fri, 17 Nov 2006 17:13:02 +0000 Received: from dev02lt by webmail.localmatters.com; 17 Nov 2006 10:14:17 -0700 Subject: RE: How to use DaoManager -- single or more From: Chris Lamey Reply-To: clamey@localmatters.com To: user-java@ibatis.apache.org In-Reply-To: <8CA0DB1C6F90AD4FA258843E456E0B5304BB9E75@igtechnexc01.igatecorp.com> References: <8CA0DB1C6F90AD4FA258843E456E0B5304BB9E75@igtechnexc01.igatecorp.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Local Matters, Inc. Date: Fri, 17 Nov 2006 10:14:16 -0700 Message-Id: <1163783656.3171.1.camel@dev02lt.corp.localmatters.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.3 (2.6.3-1.fc5.5) X-Virus-Checked: Checked by ClamAV on apache.org No, it's threadsafe. One rollback/commit on one thread won't affect something going on in another thread. On Fri, 2006-11-17 at 22:23 +0530, Tamilselvan Radha Krishnan wrote: > Tony, > We have already started the work and currently using the DAOManager per > user. I read that it can be loaded once while application started and > can be used simultaneously. But I'm starting/closing transaction using > daoMgr.startTransaction() and daoMgr.endTransaction() to commit or roll > back the changes. > > If we use single DaoManager, then shouldn't it commit or rollback the > transactions for all the user who are using the same DaoManager? > > Thanks in advance. > > Regards, > > Tamil > > > -----Original Message----- > From: Tony Qian [mailto:daqiqian2@aol.com] > Sent: Friday, November 17, 2006 10:00 PM > To: user-java@ibatis.apache.org > Subject: Re: How to use DaoManager -- single or more > > Tamil, > > If you just started, it's better to integrate iBATIS with Spring DAO. > I noticed from mailing list that iBATIS team is going to deprecate the > iBATIS DAO. > > Tony > > Tamilselvan Radha Krishnan wrote on 11/17/2006, 10:36 AM: > > > Hi, > > We are newly using ibatis framework as DAO layer for our work. I > > understand that DaoManager can be used create DAO references. Also > it > > is used to control the database JDBC transactions as well like > > Connection in JDBC. > > > > My question is should I maintain one DaoManager for all users. Or > each > > user would require one DaoManager.? My application require more > > transactions to be handled. > > > > Please advise me. > > > > Regards, > > > > Tamil > > > > > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > > > Information transmitted by this EMAIL is proprietary to iGATE Group > of > > Companies and is intended for use only by the individual > > or entity to whom it is addressed and may contain information that is > > privileged, confidential, or exempt from disclosure under > > applicable law. If you are not the intended recipient of this EMAIL > > immediately notify the sender at iGATE or mailadmin@igate.com > > and delete this EMAIL including any attachments > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > > > > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ > > Information transmitted by this EMAIL is proprietary to iGATE Group of Companies and is intended for use only by the individual > or entity to whom it is addressed and may contain information that is privileged, confidential, or exempt from disclosure under > applicable law. If you are not the intended recipient of this EMAIL immediately notify the sender at iGATE or mailadmin@igate.com > and delete this EMAIL including any attachments > _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ >