Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user-java@ibatis.apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Message-ID: <8199910.post@talk.nabble.com>
Date: Sat, 6 Jan 2007 15:36:12 -0800 (PST)
From: ajoo <ajoo.email@gmail.com>
To: user-java@ibatis.apache.org
Subject: Re: NPE when using user connection and sub-select statement
In-Reply-To: <a10a823c0701060838u28b1964vdbb58d030478f39d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <8195657.post@talk.nabble.com>
 <a10a823c0701060838u28b1964vdbb58d030478f39d@mail.gmail.com>


Larry Meadors-2 wrote:
> 
> I was in a similar position, but was able to make that "connection
> manager" look like a javax.sql.DataSource and use it that way with
> iBATIS.
> 
> You should investigate doing that with yours - it's actually pretty
> simple, there are only 6 methods in the interface (well, a couple more
> with JDBC4, but you're probably not there yet).
> 
> The chief advantage of doing that is that it will get you *completely*
> out of the connection management business - you can let iBATIS handle
> it all, which will VASTLY simplify your entire system.
> 
> Larry
> 

Thanks Larry. I suppose you are talking about the DataSourceFactory
interface? I'll definitely give it a try. It sounds like many of my ibatis
integration code can be go away this way, which will be great.


By the way, if you are concerned about versioning problem with DataSource,
check out http://dimple.codehaus.org, it allows one to implement only the
relevant methods and leave the irrelevant UnsupportedOperationException.

Ben


-- 
View this message in context: http://www.nabble.com/NPE-when-using-user-connection-and-sub-select-statement-tf2931416.html#a8199910
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.