> I do understand advantages of using bean with CompoundPropertyModel, Or regular property models even.
> 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. What Igor said: > bean.getdate() if you are using a bean, or just date if you are binding to a property on the form subclass vs (Date)textbox.getModelObject(); which requires you to keep a reference to the textbox component anyways. and it is also more elegant to e.g. create a copy constructor or utility object for copying so that you don't have your submit method littered with code to copy properties. That's largely a matter of taste though. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
