What is STATE_SAVING_METHOD parameter in JSF 2.0

by 
java.io.NotSerializableException

This kind of exception has usually a message in the root cause which shows the fully qualified class name of the class which doesn’t implement Serializable. You should pay close attention to this message to learn about which class it is talking about and then let it implement Serializable accordingly.

Often, making only your managed bean classes serializable is not always sufficient. You also need to ensure that each of its properties is also serializable. Most standard types like String, Long, etc implement all already Serializable. But (custom) complex types such as nested beans, entities or EJBs should each also be serializable. If something is not really implementable as Serializable, such as InputStream, then you should either redesign the model or make it transient (and keep in mind that it will be null after deserialization).

What is the difference when i use client and server

First some background information: Why JSF saves the state of UI components on server?

The main technical difference is that the client setting stores the entire view state as the value of the javax.faces.ViewState hidden input field in the generated HTML output and that the server setting stores it in the session along with an unique ID which is in turn referenced as the value of the javax.faces.ViewState hidden input field.

So, setting to client increases the network bandwidth usage but decreases the server memory usage and setting to server does the other way round. Setting to client has however an additional functional advantage: it prevents ViewExpiredExceptions when the session has expired or when the client opens too many views.

More Related Contents:

  1. When to use , tag files, composite components and/or custom components?
  2. JSF component binding without bean property
  3. JQuery Conflicts with Primefaces? [duplicate]
  4. Should PARTIAL_STATE_SAVING be set to false?
  5. Localizing enum values in resource bundle
  6. JSF implicit vs. explicit navigation
  7. How to get rid of WARNING: PWC4011: Unable to set request character encoding to UTF-8
  8. Primefaces static and dynamic columns in datatable
  9. Work around for faulty INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL in Mojarra JSF 2.1
  10. Is JSF 2.0 View Scope back-button safe?
  11. Depedency inject request parameter with CDI and JSF2
  12. Invoke method with varargs in EL throws java.lang.IllegalArgumentException: wrong number of arguments
  13. How to find indication of a Validation error (required=”true”) while doing ajax command
  14. JSF facelets template packaging
  15. Difference between @Named and @ManagedBean annotations in JSF2.0 Tomcat7 [duplicate]
  16. CDI Injection into a FacesConverter
  17. Update component after file download
  18. Passing the backing bean as a parameter to a Facelet include
  19. When to use f:view and f:subview
  20. How to use JSF versioning for resources in jar
  21. Primefaces datatable frozen columns misallignment
  22. Create table columns dynamically in JSF
  23. Passing parameter to JSF action
  24. Display Current Date on JSF Page
  25. Object in Flash scope is not available after redirect
  26. How to keep JSF flash scope parameters on page reload?
  27. Primefaces dialog + commandButton
  28. Primefaces DataTable, lazy loading and CommandButton per row
  29. f:viewParam doesn’t pass required parameter when new xmlns.jcp.org namespace is used
  30. Primefaces’s dialog ‘appendTo’ property, what it useful for?

Leave a Comment