> From: Peter Donald [mailto:[EMAIL PROTECTED]] > > On Thu, 26 Sep 2002 01:47, [EMAIL PROTECTED] wrote: > > 1.1 > > > jakarta-avalon-excalibur/event/src/java/org/apache/excalibur/m > pool/PoolUtil > >.java > > > > Index: PoolUtil.java > > > =================================================================== > > /* > > * Created by IntelliJ IDEA. > > * User: bloritsch > > * Date: Sep 25, 2002 > > * Time: 11:47:49 AM > > * To change template for new class use > > * Code Style | Class Templates options (Tools | IDE Options). > > */ > > LICENSE!
Oops. (As you can see I have an early adopters version of IDEA) Will fix ASAP. > > > I would prefer that you checked if it implemented Recyclable > class (also by > reflection). The reason being that I have classes that have a > recycle method > that are not Recyclable. Hmm. We need to support the Recyclable interface from the old Pool package without an artificial dependency for one class.... So we can choose to use a particular "recycle" method even if it is "reset" or whatever using pure reflection. Any thoughts on how to satisfy it without crazy dependency checks? I can add the check for the "Recycle" interface as well. How do you feel about a "Resettable" interface for MPool, which will allow PoolUtil to check for the Resettable interface or the old Recyclable interface. That way we can make them both work.... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
