Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 32431 invoked from network); 18 Oct 2002 21:16:01 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 18 Oct 2002 21:16:01 -0000 Received: (qmail 15436 invoked by uid 97); 18 Oct 2002 21:16:51 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 15420 invoked by uid 97); 18 Oct 2002 21:16:51 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 15408 invoked by uid 98); 18 Oct 2002 21:16:50 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [beanutils] ready for 1.5 release? X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Fri, 18 Oct 2002 14:16:00 -0700 Message-ID: <458473676F1AC74A84EAB2F22004DA6D53132F@mail.nextance.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [beanutils] ready for 1.5 release? Thread-Index: AcJ22L+QZ2YpW6brTz2I3czWEZm9CwAEp6Sg From: "Scott Sanders" To: "Jakarta Commons Developers List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > This is an area that I've often wondered about -- how do most=20 > people deal with writing unit tests for this sort of stuff? >=20 In this situation, I suppose you could do some classloader tricks to reload the same class with a different method signature, which would make the call fail the second time, but that seems like a hell of a lot of work. I say we patch this particular one without a test case. Scott -- To unsubscribe, e-mail: For additional commands, e-mail: