|
From: Jan H. (JIRA) <no...@sp...> - 2008-03-18 07:22:18
|
[ http://jira.springframework.org/browse/RCP-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Hoskens updated RCP-108:
----------------------------
Fix Version/s: (was: 1.0.0)
1.0.1
> Add collection support to FormModel architecture
> ------------------------------------------------
>
> Key: RCP-108
> URL: http://jira.springframework.org/browse/RCP-108
> Project: Spring Framework Rich Client Project
> Issue Type: New Feature
> Components: Binding System
> Reporter: Scott Russell
> Assignee: Oliver Hutchison
> Fix For: 1.0.1
>
>
> Currently, the creation of Forms and FormModels centres around a single form object being edited. Validation and commit/revert logic also revolve around this principle.
> At least two use cases exist where one would want to have a FormModel wrapping a collection of form objects, rather than a single form object.
> a) User edits a (top-level) collection of form objects (eg. in an editable JTable), then wants to commit/revert all edited objects. Validation rules should be able to apply to all elements in collection, and to the collection as a whole. Thus validation feedback, and form guards, can be aware of validation state of all form objects.
> b) User edits a top-level form object, which has a (detail) property of type Collection. This property could for example be displayed in an editable JTable (or JTree or TreeTable). Validation rules should be able to be applied to all elements in the collection individually, and to the collection as a whole (eg. size must > 1, etc). This allows for validation feedback and enablement/disablement of form guards.
> -Scott
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.springframework.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
|