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.
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"? Wendy, if you can get Struts working my hat is off to you. While Struts is not difficult to get working it is so flexible and feature rich that you can really wide yourself up if you are not careful. So I applaud anyone that can make your statement! ;-) Thanks, Kenneth. ----- Original Message ----- From: "Wendy Smoak" <[EMAIL PROTECTED]> To: "'Jakarta Commons Users List'" <[EMAIL PROTECTED]> Sent: Wednesday, July 02, 2003 12:04 PM Subject: RE: [beanutils] not finding the setter > Kenneth wrote: > > Thanks Wendy and Jose for responding. > > Point taken. My bean is not in fact a valid bean. > > I didn't read far enough. It's true that the class you posted isn't valid, > but not for the reason I stated. It's not because of the three methods. > It's the types that are causing the problem. Make them all boolean and I > think you'll have a valid Bean again. > > Section 8.3.2 says: > " This is<PropertyName> method may be provided instead of a > get<PropertyName> method, > or it may be provided in addition to a get<PropertyName> method. In either > case, if the is<PropertyName> method is present for a boolean property then > we will use the is<PropertyName> method to read the property value. " > > I only know enough about this to get a Struts app to work. :) > > -- > Wendy Smoak > Applications Systems Analyst, Sr. > Arizona State University, PA, IRM > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
