Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 399381 - Bean-based table field data and name-based import/export of table data
Summary: Bean-based table field data and name-based import/export of table data
Status: CLOSED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Scout (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 384479
  Show dependency tree
 
Reported: 2013-01-29 08:36 EST by Andi Bur CLA
Modified: 2021-08-19 11:13 EDT (History)
0 users

See Also:
andi.bur: juno+
andi.bur: kepler+


Attachments
applied patch (60.10 KB, patch)
2013-01-29 11:40 EST, Andi Bur CLA
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Andi Bur CLA 2013-01-29 08:36:42 EST
The contents of an ITable can be imported from and exported to an AbstractTableFieldData which stores the table data within a list of object arrays. The import and export routines are index-driven, based on IColumn indexes. This kind of data structure makes it very hard to extend (e.g. adding additional columns at arbitrary indexes to an existing table using subclassing).

To solve this limitation, add the option to use a bean-based table field data. Every row should be represented by a bean and the import and export to and from an ITable should be based on property names and IColumn.getColumnId().

Further columns of an ITable can be replaced by subclasses using @Replace. However, the data type of a replaced column cannot be changed. Hence the row data must not contain new properties for replaced columns.

Scout SDK: add a new source builder for generating bean-based table field data classes. The default is still to generate an object array based AbstractTableFieldData.
Comment 1 Andi Bur CLA 2013-01-29 11:40:39 EST
Created attachment 226271 [details]
applied patch

patch implementing the requirements described above
Comment 2 Andi Bur CLA 2013-01-29 11:41:20 EST
applied attached patch on Scout branch 3.8. Merge to 3.9 will be done automatically.
Comment 3 Matthias Zimmermann CLA 2013-03-04 06:11:32 EST
Bug closed, shipped with 3.8.2 (Juno, SR2)