On Jan 20, 2012, at 2:48 PM, Mark Thomas <[email protected]> wrote:
> On 20/01/2012 20:19, Gary Gregory wrote: >> On Fri, Jan 20, 2012 at 1:59 PM, Sandeep More <[email protected]> wrote: >> >>> >>> On Jan 20, 2012, at 12:43 PM, Gary Gregory <[email protected]> wrote: >>> >>>> On Jan 20, 2012, at 13:29, Sandeep More <[email protected]> wrote: >>>> >>>>> Thanks Gary, >>>>> Sorry for not being clear with my question. You are right, clear() >>> method >>>>> calls the destroyObject() method but only for the objects sitting idle >>> in >>>>> the pool. >>>>> >>>>> What I want is a way to call destroyObject() method on all the objects >>> in >>>>> the pool (including the active abjects). >>>> >>>> Do you mean the objects that have borrowed out of the pool? >>> >>> Yup ! >>> >>>> The pools >>>> do not track objects once they are borrowed out. The pools start >>>> tracking an object again once returned. >>>> >>>> I think this might change in 2.0... >>> >>> So, there is no way for a pool to call destroyObject() method on active >>> objects currently right ? >>> >> >> That's how I understand it. Anyone else? > > Correct. In pool 1.x once an object leaves the pool, there is no way for > the pool to track that object. > > In pool 2.x it will be possible to do this as active, idle and all > objects may be obtained from the pool. > > One way to work around this in poll 1.x is to modify your object factory > to keep a reference to the objects it has created. Great ! Thanks Mark. I'll probably have to do that. > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
