In fact, I'd like to merge the ValidatorForm with the DynaActionForm configuration, so we'd have a central place to define everything the framework wants to know about a form.
On the topic of form processing, I'd also like to add a populate method that the Request Processor could call, instead of doing it externally, so a form could populate itself.
-Ted.
Don Brown wrote:
Hmm...I'm not familiar with that discussion, but I don't see why general form functionality couldn't be defined in an interface, but the ActionForm left how it is. Of course we also have a chance to do what Craig said he'd change about Struts (at JavaOne 2003 JSF BOF) and combine forms and actions. WebWork2/XWork seems to have done well with that approach.
Again, just throwing ideas out there :)
Don
On Wed, 17 Dec 2003, Edgar P Dollin wrote:
And you're really going to have to break both of my arms and/or kick me out of Struts development if you want ActionForm *ever* changed to an interface again -- in *any* future Struts release. I think it's an absolutely horrible idea, for reasons that have been documented way too many times to count.
Craig McClanahan
- Also, again totally agreeing with Ted, make everything interface based,
a few more hears here ;^)
Joe Germuska
The interface discussion has come up previously and there was some emotion tied to it.
Edgar
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
