11 Edu447fy

Copyright 2007, Oracle. All rights reserved.
R12 Building OA Framework Applications

Implementing a Delete
Copyright 2007, Oracle. All rights reserved. 11 - 2
Lesson Objectives
After completing this lesson, you should be able to:
Create a typical OA Framework delete page
Describe error handling within OA Framework
Error Handling Overview
Exception types
Exception classes
Bundled exceptions
Dialog pages and message boxes
Debugging messages
Exception Types
General
BC4J throws an implicit (runtime) JBOException
type exception.
OAException is a specialization of JBOException
that can use the AOL Message Dictionary.
Throw OAException for general page-level errors.
Validation
Throw from entity objects and view objects for row
and attribute level failures.
Throw OAAttrValException for attribute level
failures.
Throw OARowValException for row (entity) level
failures.
Exception Types
Severe (fatal)
System-level errors like NullPointerException
Some JBO exceptions like NoDefException
Provides a user-friendly generic message with a
link to the error stack
Oracle Workflow notification
Seeded business event
oracle.apps.fnd.framework.OAFatalError
sends report of fatal error, including error stack, to
SYSADMIN user (if subscribed). Subscription to
this event is disabled by detault.
Exception Classes
Message Types
The OAException, OAAttrValException, and
OARowValException classes can have a message type
parameter.
OAException.ERROR
OAException.WARNING
OAException.INFORMATION
OAException.CONFIRMATION
OAException.SEVERE
Message Dictionary
Message Dictionary stores messages in one place for the
following reasons:
Allows those messages to be used in all your
applications.
Provide a consistent look and feel for messages within
and across your applications.
Messages can be changed or translated without
regenerating or recompiling your applications code.
Allows flexible messages that can include context-
sensitive variable text.
Implementing Message Dictionary
1. Define your message.
Include variable tokens for runtime substitution of
values.
2. Determine the exception class.
3. Determine the message type.
4. Set-up the exception and the tokens passed to the
message.
5. Test for the exception condition, and throw the
exception as needed.
Instantiating Attribute-level Exceptions
To instantiate an attribute-level exception, you must pass the
following information:
Source object type (OAException.TYP_ENTITY_OBJECT or
OAException.TYP_VIEW_OBJECT)
Full entity definition name or view instance name as
appropriate
Primary key of the entity or row
Attribute name being validated
Attribute value that failed validation
Error message application short name
Error message name
Instantiating Row-level Exceptions
To instantiate a row-level exception, you must pass the
following information:
Full entity definition name or view instance name as
appropriate
Primary key of the entity or row
Error message application short name
Error message name
Attribute Value - EO Example
public void setSalary(Number value) {
if (value != null) {
if (value.compareTo(0) <= 0) {
throw new OAAttrValException(
OAException.TYP_ENTITY_OBJECT,
getEntityDef().getFullName(),
getPrimaryKey(),
"Salary",
value,
"AK",
"FWK_TBX_T_EMP_SALARY_REQUIRED");
}
setAttributeInternal(SALARY, value);
}
} // end setSalary()
Attribute Value - VO Example
public void setDescription(String value) {
if("XXX".equals(value) {
throw new OAAttrValException (
OAException.TYP_VIEW_OBJECT,
getViewObject().getFullName(),
getKey(),
"Description",
value,
"FND",
"ATTR_EXCEPTION");
}
setAttributeInternal("Description", value);
} // end setDescription()
Row Value - EO Example
protected void validateEntity() {
super.validateEntity();
if (attr1!=attr2)
throw new OARowValException (
getEntityDef().getFullName(),
getPrimaryKey(),
"FND",
"ATTR_EXCEPTION");
}
Row Value - VO Example
protected void validate() {
super.validate();
if (attr1!=attr2)
throw new OARowValException (
getViewObject().getFullName(),
getKey(),
"FND",
"ATTR_EXCEPTION");
}
Messaging Flows
There are two kinds of message flows:
Inline Message the message appears inline on a page
around the region item that requires attention. The inline
message is also repeated in the message box at the top of
the page.
Dialog Page the message appears on its own dialog
page in the flow.
Inline Messages
Dialog Pages
processFormRequest(OAPageContext pageContext, OAWebBean
webBean) {
// Get the purchase order number from the request.
String empNumber =
pageContext.getParameter(EmployeeId");
MessageToken[] tokens = {
new MessageToken(EMP_NUMBER", empNumber)};
OAException message = new OAException("ICX",
"FWK_TBX_T_PO_UPDATE_CONFIRM", tokens,
OAException.CONFIRMATION, null);
pageContext.putDialogMessage(message);
}
Dialog Pages
processFormRequest(OAPageContext pageContext, OAWebBean
webBean) {
OAException descMesg = new OAException("FND",
"FND_CANCEL_WARNING");
OAException instrMesg = new OAException("FND",
"FND_CANCEL_ALERT");
String okUrl = APPS_HTML_DIRECTORY +
"OA.jsp?OAFunc=FND_REQUISITIONS_PAGE";
String noUrl = APPS_HTML_DIRECTORY +
"OA.jsp?OAFunc=FND_REQUISITIONS_PAGE&retainAM=Y";
pageContext.redirectToDialogPage(OAException.WARNING,
descMesg, instrMesg, okUrl, noUrl);
}
Switchers
There are three types of switchers.
Application
Context
Table Content
Table Content Switcher Abilities and Limits
Table content switchers can have the following:
Column header labels set by modifying the Prompt property
for each Switcher nested region item.
Sorting for the item set by modifying the Initial Sort
Sequence property for each Switcher nested region item.
Limit the use of Switchers to within tables, advanced
tables, or HGrids, particularly when you want to switch
between different kinds of web beans, such as different
images.
Switchers can be used outside a table, but it is
recommended to use SPEL binding for the Rendered
property of the content that you want to conditionally
display.
Implementing Table Content Switchers
Declaratively adding table content switchers is done as
follows:
1. Update the VO (SQL SELECT) to include a switcher
column or attribute.
2. Create a switcher region.
3. Set the default switcher case.
4. Add additional switcher cases to the switcher region.
5. If needed, align the switcher images within your table.
Query Page with Non-Deleteable Employee
Once you complete the lab, your Search page should look
similar to the following for an employee that is not
deleteable.
Query Page with Deleteable Employee
Once you complete the lab, your Search page should look
similar to the following for an employee that is deleteable.
Warning Dialog
Once you complete the lab, your Warning dialog on
attempting a delete should look similar to the following:
Confirmation Message
Once you complete the lab, your Search page should
provide a confirmation similar to the following of a success
deletion.
Summary
In this lesson, you should have learned how to:
Create a typical OA Framework delete page.
Describe error handling within OA Framework.

11 Edu447fy

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

11 Edu447fy

Transféré par

Droits d'auteur :

Formats disponibles

Copyright 2007, Oracle. All rights reserved.

R12 Building OA Framework Applications

Vous aimerez peut-être aussi