You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the issue's title already tells the first ajax call set's the view parameters while subsequent requests do not. The problem is easily reproducible. I'm using Wildfly 19.0 which includes Mojarra 2.3.9.SP06 in my test setup.
You can expose the bug now by opening https://localhost:8443/test/test.xhtml?param=foo in your browser. As expected the log claims that the view parameter was set to "foo". Now when you first press the button the log again claims that param was set to "foo" proving that the setter was called again. This is unexpected and should not happen from my point of view. It's even more puzzling, that every subsequent button press does not cause the setter to called again. Even stranger the first and all subsequent calls look exactly alike but cause different behavior on the server side.
My expectation was that view parameters never get set by ajax calls because the forms action url does not contain the view parameters. I could also live with ajax calls always setting the view's parameters again. Having the first ajax call behave differently than the subsequent ones is irritating to say the least.
As the issue's title already tells the first ajax call set's the view parameters while subsequent requests do not. The problem is easily reproducible. I'm using Wildfly 19.0 which includes Mojarra 2.3.9.SP06 in my test setup.
I have the following bean:
I also have simple .xhtml page which contains one button that fires an ajax request:
You can expose the bug now by opening https://localhost:8443/test/test.xhtml?param=foo in your browser. As expected the log claims that the view parameter was set to "foo". Now when you first press the button the log again claims that param was set to "foo" proving that the setter was called again. This is unexpected and should not happen from my point of view. It's even more puzzling, that every subsequent button press does not cause the setter to called again. Even stranger the first and all subsequent calls look exactly alike but cause different behavior on the server side.
My expectation was that view parameters never get set by ajax calls because the forms action url does not contain the view parameters. I could also live with ajax calls always setting the view's parameters again. Having the first ajax call behave differently than the subsequent ones is irritating to say the least.
See also this stackoverflow question for a discussion about the issue.
The text was updated successfully, but these errors were encountered: