If the value of a data table has request scope, be sure that the data does not change between the rendering of the table and the decoding of the
response. If the new data set is different, then the wrong row will be processed. If the new data set is empty, then no action takes place at all
because no matching link is encountered.
Himai Minh wrote:Hi, Tim. Thanks for the explanation.
To make sure I understand the explanation.
You mean if we edit a row in a data table and click on the row's submit button, there is a new request object created behind the scene ?
In the case, the request object with the original data is lost?
As far as losing track of what row you're working on, that was the original point. The cursor information used to do such things is lost when you run in request scope.
It will give me the powers of the gods. Not bad for a tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your databasehttps://coderanch.com/t/704633/RavenDB-Open-Source-NoSQL-Database