Package org.eclnt.jsfserver.util

Class CCStateManager

java.lang.Object

org.eclnt.jsfserver.base.faces.application.StateManager

org.eclnt.jsfserver.util.CCStateManager

public class CCStateManager
extends StateManager

State manager that is used within CaptainCasa. The situation is: CaptainCasa components do not hold any state (aside technical state) on their owns, the full application state is always referenced via expressions. Therefore the strategy is:

The view root is parked within the session state of the http session. Assuming that the next http request will hit the same virtual machine the view root will as consequence NOT be persisted all the time but is kept stable.

If case the session state is not available (e.g. due to session migration) the view root will be re-built out of the current page context.

What's the advantage? There is NO UIComponent state serialization with every roundtrip. So, the scenario is "optimal" if the session by default is kept up and running in a cerain application server node.

Whats's the disadvantage? If a session is migrated from one node to the next, then the current request that the user invoked will be lost (because there is no component tree to take over events and data changed - the tree is rebuilt in the rendering phase).

Nested Class Summary

Nested classes/interfaces inherited from class org.eclnt.jsfserver.base.faces.application.StateManager

StateManager.SerializedView

Constructor Summary

Constructors

Constructor	Description
CCStateManager(StateManager parent)

Method Summary

Modifier and Type	Method	Description
protected Object	getComponentStateToSave(FacesContext context)
protected Object	getTreeStructureToSave(FacesContext context)
boolean	isSavingStateInClient(FacesContext context)
protected void	restoreComponentState(FacesContext context, UIViewRoot viewRoot, String renderKitId)
protected UIViewRoot	restoreTreeStructure(FacesContext context, String viewId, String renderKitId)
UIViewRoot	restoreView(FacesContext context, String viewId, String renderKitId)
StateManager.SerializedView	saveSerializedView(FacesContext context)
Object	saveView(FacesContext context)
void	writeState(FacesContext context, Object state)
void	writeState(FacesContext context, StateManager.SerializedView state)

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

CCStateManager

public CCStateManager(StateManager parent)

Method Details

restoreView

public UIViewRoot restoreView(FacesContext context,
 String viewId,
 String renderKitId)

Overrides:

restoreView in class StateManager

saveView

public Object saveView(FacesContext context)

Overrides:

saveView in class StateManager

isSavingStateInClient

public boolean isSavingStateInClient(FacesContext context)

Overrides:

isSavingStateInClient in class StateManager

writeState

public void writeState(FacesContext context,
 Object state)
                throws IOException

Overrides:

writeState in class StateManager

Throws:

IOException

writeState

public void writeState(FacesContext context,
 StateManager.SerializedView state)
                throws IOException

Overrides:

writeState in class StateManager

Throws:

IOException

saveSerializedView

public StateManager.SerializedView saveSerializedView(FacesContext context)

Overrides:

saveSerializedView in class StateManager

getTreeStructureToSave

protected Object getTreeStructureToSave(FacesContext context)

Overrides:

getTreeStructureToSave in class StateManager

getComponentStateToSave

protected Object getComponentStateToSave(FacesContext context)

Overrides:

getComponentStateToSave in class StateManager

restoreTreeStructure

protected UIViewRoot restoreTreeStructure(FacesContext context,
 String viewId,
 String renderKitId)

Overrides:

restoreTreeStructure in class StateManager

restoreComponentState

protected void restoreComponentState(FacesContext context,
 UIViewRoot viewRoot,
 String renderKitId)

Overrides:

restoreComponentState in class StateManager