Re: commandLink not working inside

[Saul Qunming Yuan]

The getter method (let's say method A) to get the data to populate the table is not the method (let's say B) that the commandLink would call. This is the traditional master - detail senario. So when the commandLink is clicked to call method B, it shouldn't care about method A, should it? Are you saying that when I click the commandLink, the getter method A will be called (to re-construct the table, i guess)? or getter method A should return the same data as the first time?   ----- Original Message ----- From: Navid Vahdat To: MyFaces Discussion Sent: Sunday, September 25, 2005 10:49 AM Subject: Re: commandLink not working inside <t:dataTable> 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.