oracle.adf.controller.faces.lifecycle.FacesPageLifecycle
ADFPhaseListener and overrides the createPageLifecycle() method to return an instance of your custom page lifecycle class.
faces-config.xml file to use your subclass of ADFPhaseListener instead of the default ADFPhaseListener. As shown in Figure 10-12, you can do this on the Overview tab of the JDeveloper faces-config.xml editor, in the Life Cycle category.
|
Note:
Make sure to replace
the existing ADFPhaseListener with your custom subclass of
ADFPhaseListener, or everything in the JSF / ADF lifecycle coordination
will happen twice!
|
SRDemoPageLifecycle class that globally overrides the reportErrors()
method of the page lifecycle to change the default way that exceptions
caught and cached by the ADF Model layer are reported to JSF. The
changed implementation reduces the exceptions reported to the user to
include only the exceptions that they can directly act upon, suppressing
additional "wrapping" exceptions that will not make much sense to the
end user.
ControllerClass attribute of the pageDefinition to identify a class that either:
oracle.adf.controller.v2.PageController class
oracle.adf.controller.v2.PagePhaseListener interface
ControllerClass attribute can either be:
ControllerClass,
it is possible to specify the name of a custom page controller class
(or page phase listener implementation) that you've configured as a
managed bean in the faces-config.xml file. This includes a backing bean for a JSF page, provided that it either extended PageController or implements PagePhaseListener.
|
Note:
When using an EL expression for the value of the ControllerClass attribute, the Structure window may show a warning, saying the "#{YourExpression}" is not a valid class. You can safely ignore this warning.
|
rangeSize property defines how many rows per page it makes
available to display in the user interface. If your page definition
contains either an iterator binding named SomeViewIter or a table binding named SomeView, you can reference the following EL expressions:
#{bindings.SomeViewIter.rangeSize}
#{bindings.SomeView.rangeSize}
#{bindings.SomeViewIter.estimatedRowCount}
#{bindings.SomeView.estimatedRowCount}
#{bindings.SomeViewIter.rangeStart + 1}
#{bindings.SomeView.rangeStart + 1}
#{bindings.SomeViewIter.rangeStart + bindings.SomeViewIter.rangeSize}
#{bindings.SomeView.rangeStart + bindings.SomeView.rangeSize}
#{bindings.SomeViewIter.rangeStart + bindings.SomeViewIter.currentRowIndexInRange + 1}
#{bindings.SomeView.currentRowIndex + 1}
Source:http://docs.oracle.com/html/B25947_01/bcdcpal005.htm#sthref826
- (This link has been lost via the removal of OraBlogs. Contact Frank Nimphius for assistance in retrieving this post)
- How To Support Dynamic JDBC Credentials (Avrom Roy-Faderman, Michael Gantman, and John Smiljanic)
ProdId attribute of the ServiceRequest entity object. This validation rule has been selected to enforce that the value lie between 100 and 999
inclusive. When you add a validation rule, you also can enter an error
message that will be shown to the user if the validation rule fails.
OnPageLoadBackingBeanBase class in the oracle.srdemo.view.util package that implements the PagePhaseListener interface described above using code like what's shown in Example 10-2. The class implements the interface's beforePhase() and afterPhase() methods so that in invokes an onPageLoad() method before the normal ADF prepare model phase, and an onPagePreRender() method after the normal ADF prepare render phase.
// In class oracle.srdemo.view.util.OnPageLoadBackingBeanBase
/**
* Before the ADF page lifecycle's prepareModel phase, invoke a
* custom onPageLoad() method. Subclasses override the onPageLoad()
* to do something interesting during this event.
* @param event
*/
public void beforePhase(PagePhaseEvent event) {
FacesPageLifecycleContext ctx =
(FacesPageLifecycleContext)event.getLifecycleContext();
if (event.getPhaseId() == Lifecycle.PREPARE_MODEL_ID) {
bc = ctx.getBindingContainer();
onPageLoad();
bc = null;
}
}
/**
* After the ADF page lifecycle's prepareRender phase, invoke a
* custom onPagePreRender() method. Subclasses override the onPagePreRender()
* to do something interesting during this event.
* @param event
*/
public void afterPhase(PagePhaseEvent event) {
FacesPageLifecycleContext ctx =
(FacesPageLifecycleContext)event.getLifecycleContext();
if (event.getPhaseId() == Lifecycle.PREPARE_RENDER_ID) {
bc = ctx.getBindingContainer();
onPagePreRender();
bc = null;
}
}
public void onPageLoad() {
// Subclasses can override this.
}
public void onPagePreRender() {
// Subclasses can override this.
}
OnPageLoadBackingBeanBase
class, then it can be used as an ADF page phase listener because it
inherits the implementation of this interface from the base class. If
that backing bean then overrides either or both of the onPageLoad() or onPagePreRender()
method, that method will be invoked by the ADF Page Lifecycle at the
appropriate time during the page request lifecycle.ControllerClass attribute on the page definition in question to an EL expression that evaluates to the backing bean.
SRMain page in the SRDemo application uses the technique described in this section to illustrate writing programmatic code in the onPageLoad() method of the SRMain backing bean in the oracle.srdemo.view.backing package. Since that backing bean is named backing_SRMain in faces-config.xml, the ControllerClass property of the SRMain page's page definition is set to the EL expression "#{backing_SRMain}".
UserList view object created above, and open the SQL Statement page to introduce your named bind variables like this:select USER_ID, EMAIL, FIRST_NAME, LAST_NAME from USERS where (upper(FIRST_NAME) like upper(:TheName)||'%' or upper(LAST_NAME) like upper(:TheName)||'%') and USER_ID between :LowUserId and :HighUserId order by EMAILNotice that you reference the bind variables in the SQL statement by prefixing their name with a colon like
:TheName or :LowUserId. You can reference the bind variables in any order and repeat them as many times as needed within the SQL statement.ViewObject vo = am.findViewObject("UserList");
vo.setNamedWhereClauseParam("TheName","alex%");
vo.setNamedWhereClauseParam("HighUserId", new Number(315));
vo.executeQuery();
BEFORE INSERT FOR EACH ROW trigger. Often the trigger assigns the primary key from a database sequence using PL/SQL logic similar to this:
CREATE OR REPLACE TRIGGER ASSIGN_SVR_ID BEFORE INSERT ON SERVICE_REQUESTS FOR EACH ROW BEGIN IF :NEW.SVR_ID IS NULL OR :NEW.SVR_ID < 0 THEN SELECT SERVICE_REQUESTS_SEQ.NEXTVAL INTO :NEW.SVR_ID FROM DUAL; END IF; END;Set the Attribute Type to the built-in datatype named
DBSequence, as shown in Figure 6-14, and the primary key will be assigned automatically by the database sequence. Setting this datatype automatically enables the Refresh After Insert property.
DBSequence,
a unique negative number gets assigned as its temporary value. This
value acts as the primary key for the duration of the transaction in
which it is created. If you are creating a set of interrelated entities
in the same transaction, you can assign this temporary value as a
foreign key value on other new, related entity rows. At transaction
commit time, the entity object issues its INSERT operation using the RETURNING INTO
clause to retrieve the actual database trigger-assigned primary key
value. Any related new entities that previously used the temporary
negative value as a foreign key will get that value updated to reflect
the actual new primary key of the master.
Note:
As shown in Figure 6-14, you will typically also set the Updatable property of a DBSequence-valued primary key to Never.
The entity object assigns the temporary ID, and then refreshes it with
the actual ID value after the INSERT option. The end user never needs to
update this value.
|
jazn-data.xml
file to create enterprise roles to group users that you add to the
identity store. You can use this mechanism to assign entire groups of
users to application roles that you have defined for the purpose of
conferring access rights defined by ADF security policies, as described
in Section 30.6.3, "How to Associate Test Users with Application Roles."
