On Mon, 2003-01-27 at 03:14, Max Ischenko wrote: > Could someone explain what's the point of using MutableFormDefinition at > all? Why coudn't I just modify FormDefinition directly (like with > setFields method in my patch)?
If you change the form you have to save that changed form so you know what form definition the user submitted. I.e. the changes aren't global, they only apply to that transaction (the three-part process of form generation, validation and possible regeneration and resubmission, and then final processing). So the new mutated form gets its own ID which is recorded in the form, and gets stored for when the user submits it. Ian ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
