FormAction handles form object data binding and validation command logic in the context of flow definition controller logic. It works fine, but its approach is not very object oriented. Specifically:
a FormAction instance is shared by the entire flow (and perhaps all flows), yet the binding and validation logic it executes is typically view-state specific.
Updating different "form objects" in the same flow is a bit unwiedly, requiring multiple independent form actions to be deployed.
This issue should devise a better solution by building support for data binding and validation into the view state construct.
Keith Donald opened SWF-297 and commented
FormAction handles form object data binding and validation command logic in the context of flow definition controller logic. It works fine, but its approach is not very object oriented. Specifically:
This issue should devise a better solution by building support for data binding and validation into the view state construct.
Affects: 1.0
Issue Links:
("depends on")
@Controller
@RequestMapping
annotations for "REST-ful" flows("is depended on by")
("is depended on by")
2 votes, 3 watchers
The text was updated successfully, but these errors were encountered: