- java.lang.Object
-
- javax.faces.lifecycle.Lifecycle
-
- Direct Known Subclasses:
- LifecycleWrapper
public abstract class Lifecycle extends Object
Lifecycle manages the processing of the entire lifecycle of a particular JavaServer Faces request. It is responsible for executing all of the phases that have been defined by the JavaServer Faces Specification, in the specified order, unless otherwise directed by activities that occurred during the execution of each phase.
An instance of
Lifecycle
is created by calling thegetLifecycle()
method ofLifecycleFactory
, for a specified lifecycle identifier. Because this instance is shared across multiple simultaneous requests, it must be implemented in a thread-safe manner.
-
-
Constructor Summary
Constructors Constructor and Description Lifecycle()
-
Method Summary
All Methods Instance Methods Abstract Methods Concrete Methods Modifier and Type Method and Description abstract void
addPhaseListener(PhaseListener listener)
Register a newPhaseListener
instance that is interested in being notified before and after the processing for standard phases of the request processing lifecycle.void
attachWindow(FacesContext context)
Create or restore the
ClientWindow
to be used to display theUIViewRoot
for this run through the lifecycle.abstract void
execute(FacesContext context)
Execute all of the phases of the request processing lifecycle, up to but not including the Render Response phase, as described in the JavaServer Faces Specification, in the specified order.abstract PhaseListener[]
getPhaseListeners()
Return the set of registeredPhaseListener
s for thisLifecycle
instance.abstract void
removePhaseListener(PhaseListener listener)
Deregister an existingPhaseListener
instance that is no longer interested in being notified before and after the processing for standard phases of the request processing lifecycle.abstract void
render(FacesContext context)
Execute the Render Response phase of the request processing lifecycle, unless theresponseComplete()
method has been called on theFacesContext
instance associated with the current request.
-
-
-
Method Detail
-
addPhaseListener
public abstract void addPhaseListener(PhaseListener listener)
Register a new
PhaseListener
instance that is interested in being notified before and after the processing for standard phases of the request processing lifecycle.- Parameters:
listener
- ThePhaseListener
to be registered- Throws:
NullPointerException
- iflistener
isnull
-
execute
public abstract void execute(FacesContext context) throws FacesException
Execute all of the phases of the request processing lifecycle, up to but not including the Render Response phase, as described in the JavaServer Faces Specification, in the specified order. The processing flow can be affected (by the application, by components, or by event listeners) by calls to the
renderResponse()
orresponseComplete()
methods of theFacesContext
instance associated with the current request.- Parameters:
context
- FacesContext for the request to be processed- Throws:
FacesException
- if thrown during the execution of the request processing lifecycleNullPointerException
- ifcontext
isnull
-
attachWindow
public void attachWindow(FacesContext context)
Create or restore the
ClientWindow
to be used to display theUIViewRoot
for this run through the lifecycle. See the class documentation forClientWindow
for an overview of the feature. IfExternalContext.getClientWindow()
returns null, create a new instance ofClientWindow
using theClientWindowFactory
. If the result is non-null, callClientWindow.decode(javax.faces.context.FacesContext)
on it. Store the newClientWindow
by callingExternalContext.setClientWindow(javax.faces.lifecycle.ClientWindow)
.- Since:
- 2.2
-
getPhaseListeners
public abstract PhaseListener[] getPhaseListeners()
Return the set of registered
PhaseListener
s for thisLifecycle
instance. If there are no registered listeners, a zero-length array is returned.
-
removePhaseListener
public abstract void removePhaseListener(PhaseListener listener)
Deregister an existing
PhaseListener
instance that is no longer interested in being notified before and after the processing for standard phases of the request processing lifecycle. If no such listener instance has been registered, no action is taken.- Parameters:
listener
- ThePhaseListener
to be deregistered- Throws:
NullPointerException
- iflistener
isnull
-
render
public abstract void render(FacesContext context) throws FacesException
Execute the Render Response phase of the request processing lifecycle, unless the
responseComplete()
method has been called on theFacesContext
instance associated with the current request.- Parameters:
context
- FacesContext for the request being processed- Throws:
FacesException
- if an exception is thrown during the execution of the request processing lifecycleNullPointerException
- ifcontext
isnull
-
-
Traduction non disponible
Les API Java ne sont pas encore traduites en français sur l'infobrol. Seule la version anglaise est disponible pour l'instant.
Version en cache
21/08/2025 14:28:39 Cette version de la page est en cache (à la date du 21/08/2025 14:28:39) afin d'accélérer le traitement.Vous pouvez activer le mode utilisateur dans le menu en haut pour afficher la version plus récente de la page.
Document créé le 14/04/2008, dernière modification le 18/08/2025
Source du document imprimé : https://www.gaudry.be/java-api-javaee-rf-javax/faces/lifecycle/Lifecycle.html
L'infobrol est un site personnel dont le contenu n'engage que moi. Le texte est mis à disposition sous licence CreativeCommons(BY-NC-SA). Plus d'info sur les conditions d'utilisation et sur l'auteur.
Références
Ces références et liens indiquent des documents consultés lors de la rédaction de cette page, ou qui peuvent apporter un complément d'information, mais les auteurs de ces sources ne peuvent être tenus responsables du contenu de cette page.
L'auteur de ce site est seul responsable de la manière dont sont présentés ici les différents concepts, et des libertés qui sont prises avec les ouvrages de référence. N'oubliez pas que vous devez croiser les informations de sources multiples afin de diminuer les risques d'erreurs.