On Jan 21, 2008 9:25 PM, Eelco Hillenius <[EMAIL PROTECTED]> wrote: Instead of a massive copy action e.g. in your onSubmit, you can > use a bean that is already populated with the values.
I do understand advantages of using bean with CompoundPropertyModel, my question was related to the situation when you are forced to create your target object after the form is submitted. For instance, when you create different kinds of objects based on what exactly was submitted, or when constructor of the target object takes certain values and there're no setters for those values. Or, like in my situation, when both of those restrictions apply. Of course, maybe I'm missing something, and there's also a way to use this approach even in cases described above. -- sp
