The only scenrio I can recall is for "mapped" properties: http://issues.apache.org/bugzilla/show_bug.cgi?id=27760
(although that is now fixed in subversion) Niall ----- Original Message ----- From: "Rick Reumann" <[EMAIL PROTECTED]> Sent: Tuesday, February 28, 2006 3:39 AM I just tested again in a simplified application, and not sure what I was smoking but it seems to be working fine. Sorry to have wasted the bandwidth. (I swear though I've run into an odd situation before with an isProperty construct before with Struts... and could have sworn I just ran into it with an app I was working on at work.. I'll have to check tomorrow to see where I was screwing up.) On 2/27/06, Niall Pemberton <[EMAIL PROTECTED]> wrote: > > Are you sure it doesn't work? I haven't used a "regular" ActionForm for a > while, but I am/was convinced BeanUtils handled this, since it uses the > standard property descriptors for a bean to get the read method - which it > then invokes to get the property value. > > Niall > > ----- Original Message ----- > From: "Rick Reumann" <[EMAIL PROTECTED]> > Sent: Monday, February 27, 2006 7:11 PM > > > Are there any plans to allow boolean ActionForm bean properties to > work correctly with the isSomeProperty vs having to use > getSomeProperty? Unless I'm crazy, it seems that the property of an > html:form element has to evaluate getSomeProperty in the ActionForm in > order to work correctly. (isWhatever is valid according to the Java > bean spec isn't it?) > > -- > Rick --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
