I think this is not a good idea. You can find lot's of folks talking about application architecture in the other forum, however, so this is my 2cents.
I always have actionforms that are different than their Domain Model/Object model counterparts for the following reasons:
1. If you want to "remember" what a user types in to a form, (when a validation error occurs), you want to show the user exactly what the user typed, not what BeanUtils will convert it to.
2. What you want to do only makes sense when you have very simple screens that map 1:1 with the DB. Frequently the UI that is required does not easily map 1:1 with the db.
3. Check out some of Ted Husted's posts on why an action form is not an interface
|