Class PhaseManager
java.lang.Object
org.eclnt.jsfserver.elements.phases.PhaseManager
- All Implemented Interfaces:
Serializable
Static access to phase management. Application can attach "runnables" to
certain phases. Methods must only be called within a request processing.
The
A request is processed in three phases: "update" phase (set, set, set of properties that were changed on client side), "invoke" phase (execution of action listeners) and "render" phase (get, get, get of properties that are contained in the layout(s), so that changed are transferred back to the client processing).
The
Runnable
instance that is passed is internally registered and
executed at the appropriate point of time. After execution it is removed out
of the internal registration. In case you want a certain command to be
executed "always" you need to re-register the command with each execution.
A request is processed in three phases: "update" phase (set, set, set of properties that were changed on client side), "invoke" phase (execution of action listeners) and "render" phase (get, get, get of properties that are contained in the layout(s), so that changed are transferred back to the client processing).
- See Also:
-
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionstatic PhaseRunnables
static void
static void
static void
static void
static void
static void
static void
static void
static void
static void
static void
static void
-
Constructor Details
-
PhaseManager
public PhaseManager()
-
-
Method Details
-
runAfterUpdatePhase
-
runAfterUpdatePhase
-
runBeforeUpdatePhase
-
runBeforeUpdatePhase
-
runAfterInvokePhase
-
runAfterInvokePhase
-
runBeforeInvokePhase
-
runBeforeInvokePhase
-
runAfterRenderResponsePhase
-
runAfterRenderResponsePhase
-
runBeforeRenderResponsePhase
-
runBeforeRenderResponsePhase
-
getPhaseRunnables
- Returns:
- May return result if no runnable is defined for whole processing.
-