ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Lamey <cla...@localmatters.com>
Subject RE: How to use DaoManager -- single or more
Date Fri, 17 Nov 2006 17:14:16 GMT
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
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> 

Mime
View raw message