Michael Jouravlev wrote: > Also, Struts > is based on idea of subclassing, thus if you already subclassing > something like ValidateForm, you cannot subclass another form, which > you would want to because it has needed event handlers.
Good point. > > What if it were a solid dispatching ActionForm as you suggest? In this > case you would not be able to subclass other class like ValidateForm, > because multiple inheritance does not exist in Java. At the same time > your base ActionForm most likely would not have any functionality, > because it depends on actual data. For UI interface, if you decide to > add one event, it probably does not really matter, to use a separate > action class for that, or to override all form classes... No firm > opinion on that. > > Anyway, I agree that combining Action and ActionForm can be > beneficial, but I would not want to *replace* current Struts > Action/ActionForm combination with a solid ActionForm. True. I'm not proposing changing the Struts API. I'm just forced to use it on a project, and am looking for a way to simplify the development. Thanks for the feedback -- this has been a most interesting thread. Stephen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
