Oracle JHeadstart Developer's Guide - Downloads - Oracle

in one of the loaded faces-config files under the name “jhsPageLifecycle”. By default,
JHeadstart generates the following managed bean definitions in the JhsCommonbeans.xml:
The second managed bean named “jhsWizardPageLifecycle” is not used by default but is
generated for your convenience. This second bean also illustrates why using the
technique of looking up the PageLifecycle class through a managed bean definition is so
powerful: you can configure specific behaviors of the class without creating a subclass by
specifying managed properties. For example, you can configure the “Transaction
Completed” message or whether model validation should be performed.
By default, the generated jhsPageLifecycle managed bean references the
JhsPageLifecycle class because this is the default value of the service-level property
“Page Lifecycle class”. If you want to use a custom subclass, you can do so by creating a
java class that extends JhsPageLifecycle and specify the name of this subclass as the
value of the Page Lifecycle Class property.
If you want to use a specific PageLifecycle class for one specific group rather than the
whole application, you can do this by setting the group-level Page Lifecycle class
property. Unlike the service-level property by the same name, this property can contain
an EL expression that references your custom lifecycle managed bean definition.
The JhsPageLifecycle class, together with the bean classes in the
oracle.jheadstart.controller.jsf.bean package form the heart of the JHeadstart
Runtime, together they implement the sophisticated runtime behaviors you can generate.
JHeadstart Developer’s Guide JSF-ADF Page Lifecycle 14 - 9