Leif Mortenson wrote:
I built the org.apache.avalon.excalibur.pool.ValidatingResourceLimitingPool
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?
It would also be easy enough to send a patch to the RepeatedCommand that
manages the pool sizes so that we can check for validatable pooled
items.
Although, I do have to ask, why do you feel that you need to do this
for a component?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
