btw. simply removing the field in DefaultPool does not work either. the m_min field in AbstractPool is set after initialize() is called!
in general the package seems to be preliminary or out-dated. the roles of AbstractPool and DefaultPool seem to be nearly identical, their responsibilities are spread over both implementations. /eike "Eike Stepper" <[EMAIL PROTECTED]> schrieb im Newsbeitrag news:[EMAIL PROTECTED] > org.apache.avalon.excalibur.pool.DefaultPool shadows the field m_min > which is already (and necessarily) declared in AbstractPool. although the > value is set at construction-time of AbstractPool, it appears to be zero > when later accessed. Thus the pool limit is never enforced. That might > have been earlier observed, if the size() method would behave as expected > and return the size of only the ready list! > > regards > /eike --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
