along with the org.apache.avalon.excalibur.pool.Validatable interface a while
back to deal with this exact problem.
Looking at the code, it looks like you can call setPoolManager on your fortressContext instance while you are initializing Fortress. This lets you override the default PoolManager with one that creates Pools of the above class.
Have not tested this, so not sure if there are some points that I'm missing. Berin?
Cheers, Leif
Vjeran Marcinko wrote:
Hi.
In Fortress, one just have to change lifestyle handler to PoolableComponentHandler and releasing the instance through service manager will not erase instance, but return it to internal pool. My question - Is there some way to mark the instance as invalid thus ordering this pool to erase this instance in case this object becomes unusable anymore (similar case with db pools when db connection gets closed fvor some reason and connection object doesn't get returned to pool) ?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
