Ticket #1954 (closed defect: invalid)
Fields in an editable Table are not bound to item properties
| Reported by: | Marko Gronroos | Owned by: | Marko Gronroos |
|---|---|---|---|
| Priority: | major | Milestone: | User Interface Library 5.3.0 RC |
| Component: | Server-side framework | Version: | 5.2.5 |
| Keywords: | Cc: | ||
| Known Issue description: | |||
| Hours estimate: | Deadline (dd.mm.yyyy): | ||
| Known Issue version (since): | Known Issue title: | ||
| Hours done: | Depends to: | ||
| Affects documentation: | no | ||
| Known Issue workaround: | |||
| Affects release notes: | no | Contract: | |
Description
If you put items (such as BeanItems) in a Table and then put the Table to editable mode, the items should be bound to the fields. However, when you change the value in the fields, the value is not written to the items (for BeanItems, the setters and getters are never called).
The problem may be in IndexedContainer, which should bind IndexedContainerProperty objects to the item properties. Something strange goes on in there. When you add an item, it is associated with a new Hashtable object, which is used for storing the properties for the item. However, the properties of the actual item are not bound to anything anywhere.
See com.itmill.toolkit.tests.book.TableEditableBean? for test code.
Change History
Note: See
TracTickets for help on using
tickets.
