Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 80035 invoked from network); 17 Apr 2008 05:41:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Apr 2008 05:41:39 -0000 Received: (qmail 49209 invoked by uid 500); 17 Apr 2008 05:41:37 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 49195 invoked by uid 500); 17 Apr 2008 05:41:37 -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 49184 invoked by uid 99); 17 Apr 2008 05:41:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Apr 2008 22:41:37 -0700 X-ASF-Spam-Status: No, hits=3.7 required=10.0 tests=DNS_FROM_OPENWHOIS,FORGED_HOTMAIL_RCVD2,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates 216.139.236.158 as permitted sender) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Apr 2008 05:40:45 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JmMrp-00045m-Fk for user-java@ibatis.apache.org; Wed, 16 Apr 2008 22:41:05 -0700 Message-ID: <16739287.post@talk.nabble.com> Date: Wed, 16 Apr 2008 22:41:05 -0700 (PDT) From: Vannel To: user-java@ibatis.apache.org Subject: Re: Transaction Performance Issue In-Reply-To: <148629c20804110353i668c2d78v929f0dc14e67197a@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: vadriewyn@hotmail.com References: <16583884.post@talk.nabble.com> <148629c20804090403y6b5c2a23v8553cf64347c7052@mail.gmail.com> <16599708.post@talk.nabble.com> <001801c89b1a$746d6340$5d4829c0$@com> <16624028.post@talk.nabble.com> <148629c20804110035kd0bae2dl22b6fc52192db1d0@mail.gmail.com> <16627288.post@talk.nabble.com> <148629c20804110353i668c2d78v929f0dc14e67197a@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org can anyone tell me what the scope of a transaction is? ----- try { //execute sql int ret = insert(...); if (ret>0) { //execute some other sql update(...); } } catch { //catch errors } ----- in the above scenario, are there 2 transactions (1 for insert, 1 for update)..? or is it considered 1 transaction within a try-catch? if i am using an external transactionmanager, where does the commit come in? i don't have anything in my EJB that controls transactions. In this case, how is iBATIS handling the commits? -- View this message in context: http://www.nabble.com/Transaction-Performance-Issue-tp16583884p16739287.html Sent from the iBATIS - User - Java mailing list archive at Nabble.com.