I guess using t:add is OK as long as the grid is not performing operations
where it needs to access the property in the data source (for operations
like sorting/filtering).
Generally speaking we (@work) almost always end up using bean models,
except in the most simple cases.
--
Chris
On Thu, Ju
Thanks for the pointers, creating a BeanModel and adding my extra columns to it
sounds like the right way to go. As an emergency solution for now I'm just
going through all grids and adding the t:add columns into t:excludeSort in
order to avoid the crashes on sorting. Then I will work on the act
Just a correction, that t:add is not just unnecessary, but it will be
ignored if you specify the beanModel explicitly:
> A comma-seperated list of property names to be added to the
> org.apache.tapestry5.beaneditor.BeanModel. Cells for added columns will be
> blank unless a cell override is provi
I'm guessing that something in the sorting part attempts to pull out the
value from your passed data source (possibly coerced from a collection).
The thing is that your data source does not contain the property (as it is
synthetic) and you do not really pull the value from the data source ever,
bu
I changed my plan of finding out what causes this difference between 5.3.7 and
5.3.8. Instead I will go with some re-design, using some suggestions I got here.
However I am still very interested in knowing whether my way of defining these
t:add columns (pasted below) in general has something wro
