|
From: Steven D. <ste...@gm...> - 2005-04-07 15:10:10
|
In case of a normalized domain model wizards will typically include form fields that span beyond the single class currently created by FormAction. Creating the form object in Spring offers the advantage that related entities could be set on the form object - as required. This would for example avoid that getPerson() would return null. It's just more flexible. > > Mmm, interesting idea, but I'm not sure we should add this (e.g. why doesn't > the > BaseCommandController has this feature?). Anyway, it would be trivial to do > this > in a FormAction subclass: > |