-
1. Re: How to save extendedDataTable state w/o JSON/clientId de
ilya_shaikovsky Apr 13, 2009 6:27 AM (in response to tw)you could define Ids for the columns in order them not to be assigned automatically. Then your table should fetch saved state fine.
-
2. Re: How to save extendedDataTable state w/o JSON/clientId de
tw Apr 13, 2009 4:17 PM (in response to tw)OK, assigning explicit IDs resolves the issue of server-side identification of the columns. This leave me with 2 issues, one which does look like a bug, the other rather nice to have:
(1) The table state does not contain the sorting column and sort direction. Here is what I get:
setTableState: {"columnsVisibility":{"j_id23":"1","c
ol3":"1","col2":"1"},"columnGroupingState":{},"columnsSizeState":{"j_id23":"100"
,"col3":"100","col2":"100"},"columnsOrder":["j_id23","static2","static1","col3",
"col2"]}
(2) It would be nice to have a binding to a Java bean with respective properties, rather than a JSON string. -
3. Re: How to save extendedDataTable state w/o JSON/clientId de
nimo22 May 12, 2009 9:20 AM (in response to tw)Why not using GSON-API to save the state and switch easily from JSON to JAVA and vice versa?