All Known Implementing Classes:
BasePoolableObjectFactory, LargePoolableObjectFactory, SimpleFactory, PoolableObjectFactoryAdaptor, SimpleFactory, SmallPoolableObjectFactory, SleepingObjectFactory, SynchronizedPoolableObjectFactory
By contract, when an ObjectPool delegates to a PoolableObjectFactory ,
validateObject may also be used to test an
instance being returned to the pool
before it is passivated . It will only be invoked
on an activated instance.
validateObject,
or for reasons specific to the pool implementation.) There is no
guarantee that the instance being destroyed will
be considered active, passive or in a generally consistent state.
PoolableObjectFactory must be thread-safe. The only promise
an ObjectPool makes is that the same instance of an object will not
be passed to more than one method of a PoolableObjectFactory
at a time.
Rodney - WaldhoffSandy - McArthur$ - Revision: 480413 $ $Date: 2006-11-28 22:16:05 -0700 (Tue, 28 Nov 2006) $Pool - 1.0| Method from org.apache.commons.pool.PoolableObjectFactory Summary: |
|---|
| activateObject, destroyObject, makeObject, passivateObject, validateObject |
| Method from org.apache.commons.pool.PoolableObjectFactory Detail: |
|---|
|
It is important for implementations of this method to be aware
that there is no guarantee about what state Also, an implementation must take in to consideration that instances lost to the garbage collector may never be destroyed. |
|
|
false if obj should be destroyed. |