-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Faces 4.1: Deprecate full state saving (FSS) #1829
Comments
I like the FFS pun there :) |
For the record, these are the context params warranting removal as well
|
should we add a warning on startup when running with that configs? |
We have FSS enabled since ancient times because of cases like this (using PrimeFaces):
State saving doesn't know about the
Storing the whole state is less costly than working around this. Maybe this case is considered in newer JSF & PF versions? In JSF 2.2 the only way a component could affect state saving tree walking is by overriding |
@VsevolodGolovanov try to create a reproducer with latest PF and create a primefaces issue; might already be fixed |
Now in Mojarra as well. |
Full state saving is widely considered to be a historical mistake in Faces. Indeed, in old meeting minutes from before Faces (JSF) 1.0 it was already brought to the table that putting everything that static on the view description also in the state would be a monumental waste of resources.
We should have deprecated this a long time ago, but we simply forgot it every release.
Let's not forget this anymore, and let's actually deprecate (for removal) FFS.
The text was updated successfully, but these errors were encountered: