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 wrong or not so right or
not Tapestry-friendly. If it does, I might try to rectify that to see if that
helps.
The column is defined like this:
- In the page template, one param of the grid tag is
t:add="prop:gridAdd"
- In the page Java code, there is the corresponding
public String getGridAdd() {
return " myColumn1, myColumn2, myColumn3, myColumn4";
}
where let's say that "myColumn3" is the column whose sorting fails.
- In the page template, within the t:grid tag there is the definition of the
customized content of that column:
<p: myColumn3Cell>${ myColumn3}</p: myColumn3Cell>
- In the page Java code, there is the method returning the value for that
column:
public String getMyColumn3()
{
return aStringThatIsNeverNull;
}
Thanks in advance for any possible feedback or hint or any related thought.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
