Guys,
I'm digging in the 2.2.0.638 code to enhance it to allow for a
queryForIterator() method on the SqlMapExecuter interface and I think I might
have found a small bug.
The queryForList() with the skip and max specified doesn't seem to work when
the ResultSet is returned as an out
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 interfa
On 1/6/07, ajoo <[EMAIL PROTECTED]> wrote:
Hi, our project uses ibatis in a slightly different way. The legacy system
uses a ConnectionManager to obtain and release connections. So I had to use
SqlMapClient.openSession(Connection).
I was in a similar position, but was able to make that "connect
BTW, we are using iBatis 2.2 for Java
--
View this message in context:
http://www.nabble.com/NPE-when-using-user-connection-and-sub-select-statement-tf2931416.html#a8195681
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.
Hi, our project uses ibatis in a slightly different way. The legacy system
uses a ConnectionManager to obtain and release connections. So I had to use
SqlMapClient.openSession(Connection).
Accordiing to the javadoc, when using openSession(Connection), I need to
manage transaction myself, which I
