DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=23815>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=23815 [beanutils]PropertyUtils.getNestedProperty() doesn't allow getXxxx on Map-Instances any longer ------- Additional Comments From [EMAIL PROTECTED] 2004-07-12 03:32 ------- In addition to the fact that this breaks backwards compatibility for all Struts 1.1 users, it is also inconsistent with the way that expression language (EL) expressions have evolved in JSTL 1.0/1.1 and JSP 2.0, as well as JSF 1.0. In all of those cases, if an object is an "instanceof Map", then it is *always* treated as a Map -- any JavaBeans properties of the object are *not* accessible. The same thing applies to the standard implementation of DynaBeans (including the implementation that Struts creates for DynaActionForms) -- if it's a DynaBean, then you are always getting/setting dynamic properties; never accessing the JavaBeans properties of the implementation class. Implementing the proposed patch for nested properties still leaves things gratuitously inconsistent -- and I consider the original Struts 1.0 behavior to be the one that is incorrect. Because of these reasons, I'm opposed to changing the *default* behavior of BeanUtils as proposed. I'm fine with making it possible once we have beanification completed (and can tell the factory to give us a BeanUtils that acts a certain way) -- but in the mean time I'm -1. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
