Help to deal with the //request scoped bean behavior?

If a4j:keepAlive or ViewScoped doesn't work, then the chance is big that the data loading logic for the datamodel is wrong. Likely you're loading it inside the getter based on some parameters instead of doing it in the action method, or constructor, or PostConstruct of the bean. The getter will namely also be called during apply request values phase of the JSF lifecycle to determine the row on which the commandlink is pressed, so that JSF can determine which action needs to be invoked.

If the getter doesn't return the datamodel with the expected row, then the action simply won't be invoked.

If a4j:keepAlive or @ViewScoped doesn't work, then the chance is big that the data loading logic for the datamodel is wrong. Likely you're loading it inside the getter based on some parameters instead of doing it in the action method, or constructor, or @PostConstruct of the bean. The getter will namely also be called during apply request values phase of the JSF lifecycle to determine the row on which the commandlink is pressed, so that JSF can determine which action needs to be invoked.

If the getter doesn't return the datamodel with the expected row, then the action simply won't be invoked. Fix it accordingly. The getter should only return the bean property or at highest only do lazy loading.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.