Return-Path: <Wendy.Smoak@asu.edu>
Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Delivered-To: mailing list commons-user@jakarta.apache.org
Received: (qmail 30811 invoked from network); 2 Jul 2003 21:35:29 -0000
Received: from post2.inre.asu.edu (129.219.110.73)
  by daedalus.apache.org with SMTP; 2 Jul 2003 21:35:29 -0000
Received: from conversion.post2.inre.asu.edu by asu.edu (PMDF V6.1 #40111)
 id <0HHF00L012HGD2@asu.edu> for commons-user@jakarta.apache.org; Wed,
 02 Jul 2003 14:32:04 -0700 (MST)
Received: from mainexzz.asu.edu (mainexzz.asu.edu [129.219.10.209])
 by asu.edu (PMDF V6.1 #40111) with ESMTP id <0HHF00IKN2HGZ6@asu.edu> for
 commons-user@jakarta.apache.org; Wed, 02 Jul 2003 14:32:04 -0700 (MST)
Received: by mainexzz.asu.edu with Internet Mail Service (5.5.2653.19)
	id <M1257D3R>; Wed, 02 Jul 2003 14:32:04 -0700
Content-return: allowed
Date: Wed, 02 Jul 2003 14:31:59 -0700
From: Wendy Smoak <Wendy.Smoak@asu.edu>
Subject: RE: [beanutils] not finding the setter
To: 'Jakarta Commons Users List' <commons-user@jakarta.apache.org>
Message-id: <A7AF1AE70A8C124593A1AC831EFE46FE0116EF8A@ex3.asurite.ad.asu.edu>
MIME-version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: multipart/alternative;
 boundary="Boundary_(ID_T0WtUzFTc6Hf/keXKColOQ)"
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

--Boundary_(ID_T0WtUzFTc6Hf/keXKColOQ)
Content-type: text/plain

> I hadn't tried making the base property boolean. But my tests show 
> that a boolean works with both a get<PropertyName> and 
> is<PropertyName> specified. Its a String based property that will not 
> work. Very interesting.

That matches the JavaBeans standard-- 8.3.2 addresses boolean properties
specifically and allows is/get/set together.  But if 'is' is present, that's
the one that will be used for a boolean.

> So I guess my question for the community would is, should BeanUtils be 
> enhanced to handle the is<PropertyName> descriptor that is returned by 
> java.beans.Introspector or should it stay conforming to the "letter of 
> the standard"?

Life is much easier when everything conforms to the spec, if something is
misbehaving you can go to "the rules" and either fix your code or log a bug
for BeanUtils.

--
Wendy Smoak
Applications Systems Analyst, Sr.
Arizona State University, PA, IRM

--Boundary_(ID_T0WtUzFTc6Hf/keXKColOQ)--