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
Must "Serializable" really be the default behavior in both client and server state modes? #1127
Comments
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented SECTION: Modified FilesM jsf-ri/src/main/java/com/sun/faces/config/WebConfiguration.java
M jsf-ri/src/main/java/com/sun/faces/renderkit/ServerSideStateHelper.java
M test/agnostic/lifecycle/pom.xml
A test/agnostic/lifecycle/unserializableServerState_negative Authentication realm: <https://svn.java.net:443> Subversion Repository |
@glassfishrobot Commented
|
@glassfishrobot Commented
|
@glassfishrobot Commented |
@glassfishrobot Commented |
@glassfishrobot Commented |
|
Mojarra issue JAVASERVERFACES-2349 asks to make Mojarra conform to this spec text, In section "State Saving Alternatives and Implications" in the "Application Integration" chapter.
The default implementation Serializes the view in both the client and server modes.
This issue has a long history, dating back to summer 2007, chronicled in JAVASERVERFACES-632. In that issue, then implementation lead Ryan Lubke stated that he polled the community and the result was that enforcing serializability in all cases should be off by default.
At this point, I'd like to amend the text quoted above to be:
The default implementation Serializes the view in client mode. Serializing the view in server
mode is optional but must be possible by setting context-param javax.faces.SERIALIZE_SERVER_STATE
to true.
The text was updated successfully, but these errors were encountered: