Summary: | [DataBinding] Validation for collections | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Boris Bokowski <bokowski> |
Component: | UI | Assignee: | Boris Bokowski <bokowski> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | bradleyjames, jens, Konstantin.Scheglov, mallo.ovidio |
Version: | 3.3 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Bug Depends on: | 174421 | ||
Bug Blocks: |
(copied from the newsgroup) For conversion support see bug 174421. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. |
> If you have any input on what conversion and validation should mean in the > context of lists/sets/maps, let me know... 1. apply value conversion and validation to each member of the container (on add/set) 2. prevent member removal based on validation result 3. position dependent validation (first/last element etc.) 4. map: validate keys/values, convert values 5. validate container properties (e.g. maximum number of elements) I'm not sure what really makes sense. Currently I need only case 1. -- Gruesse/Regards, Peter Maas, Aachen