I'd like to know if it's possible to avoid using to many session scoped form beans.
I have a bean that contains a collection and I use nested:iterate to display entry fields on my html:form. When the form is submitted, I get an error in BeanUtils.populate(), because the new bean (when the bean is request scoped) contains an empty collection and populate() tries to set the properties of the elements that existed on the bean of the previous request. If I change the bean to session scope, everything works fine (because now the bean is the same for both requests), but I think it's kind of messy to have lots of session scoped beans. I'd appreciate to have any comments on this subject. Thanks Jorge Mascena --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
