Package org.apache.myfaces.renderkit
Class MyfacesResponseStateManager
java.lang.Object
jakarta.faces.render.ResponseStateManager
org.apache.myfaces.renderkit.MyfacesResponseStateManager
- Direct Known Subclasses:
- HtmlResponseStateManager
- Version:
- $Revision$ $Date$
- Author:
- Manfred Geiler (latest modification by $Author$)
- 
Field SummaryFields inherited from class jakarta.faces.render.ResponseStateManagerCLIENT_WINDOW_PARAM, CLIENT_WINDOW_URL_PARAM, NON_POSTBACK_VIEW_TOKEN_PARAM, RENDER_KIT_ID_PARAM, VIEW_STATE_PARAM
- 
Constructor SummaryConstructors
- 
Method SummaryModifier and TypeMethodDescriptionbooleanisWriteStateAfterRenderViewRequired(FacesContext facesContext) Indicates if the call to ResponseStateManager.writeState should be done after the view is fully rendered.voidsaveState(FacesContext facesContext, Object state) Execute additional operations like save the state on a cache when server side state saving is used.Methods inherited from class jakarta.faces.render.ResponseStateManagergetCryptographicallyStrongTokenFromSession, getState, getViewState, isPostback, isStateless, writeState
- 
Constructor Details- 
MyfacesResponseStateManagerpublic MyfacesResponseStateManager()
 
- 
- 
Method Details- 
saveStateExecute additional operations like save the state on a cache when server side state saving is used.
- 
isWriteStateAfterRenderViewRequiredIndicates if the call to ResponseStateManager.writeState should be done after the view is fully rendered. Usually this is required for client side state saving, but it is not for server side state saving, because ResponseStateManager.writeState could render a just a marker and then StateManager.saveState could be called, preventing use an additional buffer.- Parameters:
- facesContext-
- Returns:
 
 
-