Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 51139 invoked from network); 5 Dec 2002 18:59:23 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 5 Dec 2002 18:59:23 -0000 Received: (qmail 10313 invoked by uid 97); 5 Dec 2002 19:00:01 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 10148 invoked by uid 97); 5 Dec 2002 19:00:00 -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 10047 invoked by uid 98); 5 Dec 2002 19:00:00 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Date: Thu, 5 Dec 2002 18:59:06 +0000 Subject: Re: [beanutils] ConstructorUtils in beanutils: a bad idea Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) From: robert burrell donkin To: "Jakarta Commons Developers List" Content-Transfer-Encoding: 7bit In-Reply-To: <20021205072459.O75824-100000@icarus.apache.org> Message-Id: X-Mailer: Apple Mail (2.482) X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Thursday, December 5, 2002, at 03:25 PM, Rodney Waldhoff wrote: > Looking through the archives, I now see the thread named > "[beanutils][lang][PROPOSAL] deprecated beanutils version of MethodUtils" > [1] which apparently should have been flagged "[VOTE]", if that was > intended to be a binding vote. no, that thread wasn't binding. that's one reason why i wanted to try to engage you in debate rather than just -1'ing the commit straight away :) > I'd be OK with leaving beanutils as the repository for reflection oriented > stuff. In light of this thread, I think I'd prefer to create true > reflection oriented commons component. I'm strongly opposed to moving a > bunch of stuff into lang because it seems somehow central or widely > applicable. I'd rather see a bunch of focused modules with well defined > scope (however tiny) than a grand utilties framework, and my reading of > the commons charter says it agrees with me. though i agree about your point in general, the reflection code fits perfectly into lang's spec. they are utility classes for package java.lang. reflect. AFAIK class and reflect(ion?) were intended to be introspection-alternatives. they need to rely on solid, low level reflection utilities. - robert -- To unsubscribe, e-mail: For additional commands, e-mail: