I should build a grid with the number and type of dynamic columns. With this version of GXT you must declare the ValueProvider every time, while the previous version was possible to establish ColumnConfig (id, dimension, header) and store in the BeanModel, but now ColumnConfig (new ValueProvider), but I can not know a priori which bean will be part of the grid. There is a possibility of being able to carry out this version
In short, yes - BaseModelData and BeanModel may be gone, but the data model that GXT 3 uses is more general, and can be made to support this basic idea. That said, if you are working with a bean-like object, the work of adding a new ValueProvider method to the PropertyAccess is going to be the cleanest way of writing this - it is strongly typed, giving you compile errors if something no longer makes sense, and sometimes letting the compiler to a better job when working out how to optimize your application.