It would seem to me to be an organizational design decision.
If you share the bean, you would also have to share the validate method,
but that can be easily managed by checking the Action Mapping to see
which form is using the bean in this instance. The easiest way to do
that is by using the parameter property to indicate which "view" of the
bean should be validated. You could also use the mapping parameter in an
omnibus action to determine what processing needs to be done.
So, the trade off is whether you like to maintain fewer classes with
more properties or more classes with fewer properties.
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 737-3463.
-- http://www.husted.com/about/struts/
Felix von Delius wrote:
>
> Is there any disadvantage in *not* having separate (Form-)Beans for every form in an
>application?
>
> -Felix
