I'm using the Java Server Faces early access release, which uses beanutils v1.3.
JSF uses beanutils to set properties in a Model bean (for example, a User object in the HTTPSession). I have a bean that extends HashMap (e.g. "public class User extends HashMap"). Things work fine with beanutils v1.3 but when I swap in beanutils v1.4 or 1.5, the behavior changes. No errors are thrown but there are no calls to my bean's get/set methods and its state doesn't change. This can be easily reproduced by taking the JSF "helloDuke" example, updating commons-beanutils.jar to 1.5, and changing "public class UserNameBean" to "public class UserNameBean extends HashMap". Is this the intended behavior? Why the change from beanutils v1.3? Is it not a good practice to extend a bean from a collection class? -- Daniel [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
