------- Additional Comments From [hidden email] 2005-05-28 06:35 -------
Actually, it occurred to me that this problem only occurs for classes where the
target bean implements Map. But in that case the target bean can *overide* the
get/set methods to access its local properties if it wants. It seems entirely
appropriate to me that the target class should make this decision, ie a bean
class that implements Map should choose whether it wants to be a pure Map, or a
normal bean "backed by a map for missing properties".
The only issue is backwards support for the behaviour of beanutils as included
in Struts 1.0. And I'm puzzled about this. I've downloaded struts 1.0.2 and it
mentions nothing about being dependent on beanutils. Nor can I see any reference
to the "Struts Bean Tags" stuff that provides <bean:write>. As far as I can see,
that first appeared in Struts 1.1. But I'm not a Struts user, so I might have
got confused. Can someone clear this up?