Structure of OAF
Let us discuss about the structure of OAF.
Let us discuss about the structure of OAF.
OAF follows J2EE Architecture and
J2EE follows MVC architecture so therefore ultimately OAF follows MVC
Architecture.
The abbreviation of MVC is Model
View Controller.
MVC is the clean design interface
between Model, View, and Controller.
 |
| Structure of OAF |
Model will take care the Data Base
related Transactions, Model contains the following:
- Entity Object (EO)
- View Object (VO)
- Callable Statement (PL/SQL Statement)
- Prepare Statement (Single Select Statement)
- OADB Transactions (Oracle Apps Data Base Transactions)
View is nothing but the OAF Page Output. View is implemented by
UIX (User Interface XML).
Controller will take care of web browser activities like HTTP Get and
HTTP Post
Controller have got three methods:
- Process Request
- Process Forms Request (HTTP Get)
- Process Form Data (HTTP Post)
HTTP get: While loading the Page we
use HTTP Get.
HTTP Post : After Loading the page
if we want any changes the we use HTTP Post.
The below figure shows the
interaction between Model, View, and Controller.
 |
| MVC Architecture |
