oracle.cabo.servlet.state
Interface StateManager

All Superinterfaces:

java.io.Serializable

All Known Implementing Classes:

QueueStateManager

public interface StateManager

extends java.io.Serializable

The StateManager interface is responsible for creating State IDs, creating States, storing States, and deciding on a strategy for purging old states. Each BajaContext has one StateManager - by default, lazily retrieved from the HttpSession - which is used to analyze states on the BajaContext's StateManager.

State implementations are required to be threadsafe, and should be serializable. StateManagers don't, however, have to describe their own strategy for persistence, or whether they are used per-user or globally. The StateUtils class provides code for storing per-user StateManagers on an HttpSession.

The StateManager and State APIs do not attempt to solve the issues involved in maintaining state in a distributed applications. By themselves, they have all the advantages and drawbacks of using HttpSession.

See Also:

Page, State, MutableState

Method Summary

void	expire() Invalidate this StateManager object, and all of its children State objects.
MutableState	getNewState() Creates a new, mutable State object.
State	getState(java.lang.String id) Returns a State based on ID.
boolean	isExpired() Tests whether the StateManager has been expired.

Method Detail

expire

public void expire()

Invalidate this StateManager object, and all of its children State objects. Once a StateManager has been invalidated, it can no longer be used to retrieve States.

isExpired

public boolean isExpired()

Tests whether the StateManager has been expired.

getState

public State getState(java.lang.String id)

Returns a State based on ID.

getNewState

public MutableState getNewState()

Creates a new, mutable State object.