iBATIS should either use the same connection if one is already open, or request another one if there is no connection currently available.
Do you have a stack trace and example SQL Map files and code? Clinton On Thu, 17 Mar 2005 06:57:48 -0700, Grier, Michael <[EMAIL PROTECTED]> wrote: > I've run into problem using iBatis with an object that does lazy > loading. The scenario is a business object that has a property that is > evaluated by a dynamic SQL element. The implementation of the property > get method is that it accesses another object that may in the same > thread attempt to load data using the same SQL map config. > > The behavior of iBatis in this circumstance is that the nested execute > gets the same connection of the outer execute and ends up closing it so > that the outer call fails. > > I have several options for avoiding this problem but am wondering > whether this represents a bug in iBatis or if it is a known and accepted > limitation of the framework, or perhaps there is an obvious solution on > the iBatis side that I am missing. > > Thanks, > > Mike >
