T
- the type of objects held in this poolpublic interface PoolableObjectFactory<T>
ObjectPool
.
By contract, when an ObjectPool
delegates to a PoolableObjectFactory
,
makeObject
is called whenever a new instance is needed.
activateObject
is invoked on every instance that has been
passivated
before it is
borrowed
from the pool.
validateObject
is invoked on activated
instances to make sure
they can be borrowed
from the pool.
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.
passivateObject
is invoked on every instance when it is returned to the pool.
destroyObject
is invoked on every instance when it is being "dropped" from the
pool (whether due to the response from 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.
ObjectPool
Modifier and Type | Method and Description |
---|---|
void |
activateObject(T obj)
Reinitialize an instance to be returned by the pool.
|
void |
destroyObject(T obj)
Destroys an instance no longer needed by the pool.
|
T |
makeObject()
Creates an instance that can be served by the pool.
|
void |
passivateObject(T obj)
Uninitialize an instance to be returned to the idle object pool.
|
boolean |
validateObject(T obj)
Ensures that the instance is safe to be returned by the pool.
|
T makeObject() throws Exception
activated
. They will not be
activated before being served by the pool.Exception
- if there is a problem creating a new instance,
this will be propagated to the code requesting an object.void destroyObject(T obj) throws Exception
It is important for implementations of this method to be aware
that there is no guarantee about what state obj
will be in and the implementation should be prepared to handle
unexpected errors.
Also, an implementation must take in to consideration that instances lost to the garbage collector may never be destroyed.
obj
- the instance to be destroyedException
- should be avoided as it may be swallowed by
the pool implementation.validateObject(T)
,
ObjectPool.invalidateObject(T)
boolean validateObject(T obj)
false
if obj
should be destroyed.obj
- the instance to be validatedfalse
if obj
is not valid and should
be dropped from the pool, true
otherwise.void activateObject(T obj) throws Exception
obj
- the instance to be activatedException
- if there is a problem activating obj
,
this exception may be swallowed by the pool.destroyObject(T)
void passivateObject(T obj) throws Exception
obj
- the instance to be passivatedException
- if there is a problem passivating obj
,
this exception may be swallowed by the pool.destroyObject(T)
Copyright © 2000-2021 Apache Software Foundation. All Rights Reserved.