You'll need a datasource if you plan on useing lazy loading features.
Otherwise you'll have to disable them.
There's really no harm in providing iBATIS with access to a
datasource, as long as you're consistent. There should be one
SqlMapClient instance per datasource. So even if you provide your
Clinton,
Thanks for the quick reply.
I'm happy to report that I found a couple of places
where we weren't closing a connection properly that
fell outside our normal connection management.
I updated the code to close the connections properly
and the Exceptions are gone (Hallelujah).
One quick
Please set
More info is available in the following poorly titled wiki (my fault):
http://wiki.apache.org/ibatis/Database_20Specific_20Information
Clinton
On Fri, 28 Jan 2005 19:09:29 -0800 (PST), Mark Nabours
<[EMAIL PROTECTED]> wrote:
>
>
> Hello.
>
>
>
> We are currently developing
Hello.
We are currently developing our first application with iBATIS, and we are extremely impressed by its design and capabilities. Everything was going great until we deployed our application to WAS 5.1 utilizing a JNDI datasource.
We end up receiving the following exception:
[1/28/05 20:31:
4 matches
Mail list logo
