Saul Qunming Yuan wrote:
But before I tried upgrading to 1.1.0, commandLink worked for months WITHOUT the following:
 
* put the bean in session scope,
* carry around the bean, using t:saveState,
* set preserveDataModel to true or
 
I'm not sure what you mean by the 4th codition. My getter to the list just calls a service method to get a collection of data to be presented in the dable.
Actually that's just what i mean. Your getter returns the llist without having to process search/filter criteria first. Thus it is nothing but a facade to the your service. There might be a problem of your data changing in between two requests, though, but in my understanding the commandLink should still work most of the time.

 
 
After upgrading to 1.1.0 and then rolled back to 1.0.9, I had to use <t:saveState> to make commandLink to work. That's why I'm confused.
In that case, I'm confused, too.

Reply via email to