On 4/7/06, Carl Smith <[EMAIL PROTECTED]> wrote: > Hello folks, I got two replies, can someone else offer some more insights on > this topic?
I've written many applications that only used one ActionForm class, and just validated it differently. I find it useful to have a single object that represents a "normalized" view of the user interface. The validations follow what logical name you give the form-bean, not the binary class. Many organizations use session scope to save trips to the databse server. It's all a matter of how you want to allocate your resources. In this case, it would appear that one form is using request scope since the operation may not be completed. The session scope version evidentally represents the current state, while the request scope version represents a proposed state change. In that case, the properties might be the same, but the data would be different. In my experience, the greatest degree of confusion comes about by repeating the same facts in different places in the same application. If the choice is having the same set of properties on different ActionForm classes *versus* sharing the same set of properites through a base class, I would opt for sharing and avoid Repeating Myself. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
