Return-Path: Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 5336 invoked by uid 98); 11 Dec 2002 19:27:44 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Received: (qmail 5317 invoked from network); 11 Dec 2002 19:27:42 -0000 Received: from daedalus.apache.org (HELO apache.org) (63.251.56.142) by nagoya.betaversion.org with SMTP; 11 Dec 2002 19:27:42 -0000 Received: (qmail 74851 invoked by uid 500); 11 Dec 2002 19:26:29 -0000 Received: (qmail 74844 invoked from network); 11 Dec 2002 19:26:28 -0000 Received: from carbon.btinternet.com (194.73.73.92) by daedalus.apache.org with SMTP; 11 Dec 2002 19:26:28 -0000 Received: from host217-41-14-12.in-addr.btopenworld.com ([217.41.14.12] helo=oemcomputer) by carbon.btinternet.com with smtp (Exim 3.22 #16) id 18MCV6-0006Sb-00; Wed, 11 Dec 2002 19:26:32 +0000 Message-ID: <00d201c2a14b$9f95a9c0$0c0e29d9@oemcomputer> From: "Stephen Colebourne" To: "Jakarta Commons Users List" Cc: "Gary Gregory" References: <245A7290F0E0D311BF6E009027E7908B0613FC8C@atlanta.seagullsw.com> Subject: Re: Hierarchies not supported in ToStringBuilder.reflectionToString(this)? Date: Wed, 11 Dec 2002 19:29:27 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N From: "Gary Gregory" > The first question I have towards implementing this is whether or not to > define this as a bug or a feature request WRT backwards compatibility. > > (1) Simplest is sometimes best: This is a bug and reflectionToString() will > handle hierarchies. > (2) More complicated to use and explain: reflectionToString() will > configurable WRT superclasses, perhaps with a toggle in a style class. This > is quite more tricky, since the hook must be provided in the right place. I think #1 should be OK. Superclasses were ignored in the first cut, and really I think now that was a big bug. For more specific to strings people have the ability to use the manual fields. By the way, this affects the HashCode, Equals and CompareTo buiders as well ;-) Stephen