commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom Klaasen (TeleRelay)" <>
Subject RE: [beanutils][PATCH] PropertyUtils and indexedProperties
Date Wed, 07 Nov 2001 09:36:34 GMT
Of course I tried it, but only on Struts (not on a generic javabeans
interpreter like an IDE). And it works for a non indexed getter based on

Maybe I got the whole JavaBeans story wrong. However, if what you
describe is the case, then the JavaBeans mechanism seems even less
powerful than I thought. Seems a pity to me.

Is anybody sure that (s)he understands the JavaBeans spec, and whether
this patch is applicable?


> -----Original Message-----
> From: Rey Francois [] 
> Sent: woensdag 7 november 2001 10:22
> To: 'Jakarta Commons Developers List'
> Subject: RE: [beanutils][PATCH] PropertyUtils and indexedProperties
> Have you actually tried this code?
> I've only *briefly* looked into the JDK and BeanUtils code, 
> so I'm not 100%
> sure of this, but it seems to me that your patch may work 
> when your property
> only has non indexed getter/setter based on List, but should 
> fail if your
> property also has indexed getter/setter. In the latter case, 
> I would expect
> the JDK IndexedPropertyDescriptor class to throw an
> IntrospectionException("type mismatch between indexed and non-indexed
> methods"). Check the source of
> IndexedPropertyDescriptor.findIndexedPropertyType().
> Again, I'm not 100% sure, I would need to test this but I 
> don't have time at
> present...
> Fr.
> -----Original Message-----
> From: Tom Klaasen (TeleRelay) []
> Sent: 07 November 2001 09:55
> To: Jakarta Commons Developers List
> Subject: [beanutils][PATCH] PropertyUtils and indexedProperties
> Hi all,
> I found a glitch in the PropertyUtils: you can only get an
> indexedProperty if its container is an array. But a java.util.List is
> also indexed. So it would be logical to be able to get an element of a
> List also as an indexedProperty.
> Hence the patch attached.
> Hope you enjoy it,
> tomK
> **************************************************************
> **********
> The information in this email is confidential and is intended solely
> for the addressee(s).
> Access to this email by anyone else is unauthorised. If you are not
> an intended recipient, please notify the sender of this email 
> immediately. You should not copy, use or disseminate the 
> information contained in the email.
> Any views expressed in this message are those of the individual
> sender, except where the sender specifically states them to be
> the views of Capco.

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message