OA Framework MVC Design Pattern

MVC Stands for Model View Controller . OA Framework uses MVC Pattern where was discussed in the earlier posts.

In simple terms refer the below image for MVC role in OAF

Reason behind why MVC is used is for its

• Flexible architecture
• Easily programmable 
• Easy Manageable over complete life cycle.  

MVC is widely used and adapted which is not a standard but most web applications uses it.Now we will see in detail what each block in the above image meant

Model 

It encapsulates all Business logic in BC4J Components like VO and EO . Mainly BC4J Components will reside in Model

View 

In simple terms which presents data from model to user . View can be any mode like Desktop,Tablet or Mobile View .UIX /OA Extensions will come under View

Controller

In simple terms it will act as a glue between Model and View . All users events will be handled by Controller which will execute Business logic and Display the results/Info to View.In OAF OA Controller class files will come under this.

In the above single Node EBS instance when a user open a browser and login into EBS , Browser will first send the requests to Application server Listener which interns contacts Servlet Engine Where Model-View-Controller will reside  , Intern MDS Engine will access DB Layer to fetch page beans to build a View(HTML Page) and sends back the Page to User browser again in the same route.