Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 28368 invoked from network); 17 Nov 2008 23:04:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Nov 2008 23:04:29 -0000 Received: (qmail 94432 invoked by uid 500); 17 Nov 2008 23:04:35 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 94414 invoked by uid 500); 17 Nov 2008 23:04:35 -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 94402 invoked by uid 99); 17 Nov 2008 23:04:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Nov 2008 15:04:35 -0800 X-ASF-Spam-Status: No, hits=2.6 required=10.0 tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.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; Mon, 17 Nov 2008 23:03:13 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1L2D8P-0007EV-JZ for user-java@ibatis.apache.org; Mon, 17 Nov 2008 15:03:57 -0800 Message-ID: <20550206.post@talk.nabble.com> Date: Mon, 17 Nov 2008 15:03:57 -0800 (PST) From: JasonAB To: user-java@ibatis.apache.org Subject: Multiple iBatis instances MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Nabble-From: jasonab@acm.org X-Virus-Checked: Checked by ClamAV on apache.org =20 I'm writing a jar that will be internally distributed, that will use iBatis on a certain set of tables. My clients might be using JDBC, iBatis or Hibernate, so I do not want to force them to set up a SqlMapClient. I=E2=80= =99d rather set up one within my jar, and not worry about how the clients will b= e accessing the database. I'm using Spring, a Spring datasource, and Spring transactions, to wire my DAOs. Assuming that anyone sending SQL to the database is using a Spring transaction and a Spring datasource, will there be any conflicts? I don't believe this will be a problem, but I want to be absolutely sure. jason --=20 View this message in context: http://www.nabble.com/Multiple-iBatis-instanc= es-tp20550206p20550206.html Sent from the iBATIS - User - Java mailing list archive at Nabble.com.