Tamas Szabo wrote:
it seems to you ok that the
org.apache.commons.beanutils.PropertyUtils.describe(Object )
method puts the class property(coming from java.lang.Object) in the map?
I'm not sure about this, but it would be more logical for me if the
class was not in the Map(if it was not handled as a normal property).
I mean when I write a bean I declare all of the properties I want to
consider properties.
But because all the beans extend Object, I also get Object's properties.
It just doesn't seems right to me :-)
Seems perfectly reasonable to me; that's inheritance at work ;-) describe()
will pull everything that looks like a bean property as defined by the
JavaBeans spec, which includes 'class'. Why do you think this property
should be handled specially? Is having it appear in the map causing a
problem somewhere?
L.
--
Laurie, Open Source advocate, Java geek and novice blogger:
http://www.holoweb.net/laurie
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]