This content has been marked as final. Show 2 replies
Hi Sri ,
Entity Objects are basically based on one table which encapsulate the business rules. These objects are used by OAF page to perform update/insert/delete operations .
Inside EOImpl.java you will find setter() and getter () methods in java we call it as accessor and mutator , each attribute in EO is mapped to column in the data base table .
You can also generate a create () method Validate () method .
Eg : To get the sequence value in OAF you can use Create() method .
VOImpl (VO) : It just consist of an Data base sql query , you might have noticed while executing a query eg : VO.executeQuery() ;
to perform any validation it provides iteration over and access to the view rows in its result set.
VoRowImpl : Represents a single row in a view object .
You will understand better when you writing a code using voimpl /voRowimpl objects
It basically performs the Business logic , we will define all our methods to implement business logic .
Eg : you can call a method from controller and define the method Amimpl.java , you can use of initializing the query or
you do DML operation , etc ...
In summery : The main reason why we have java file distribute across EO , VO , AM is because OAF is designed with MVC design pattern ,
in other words we have to isolate the responsibility of code in each layer ( Model , View , Controller ) .Its bad practice to write
the entire code in one single class file .
Eg : Controller class should accept the parameter from user and pass these parameters BC4J files ( AMImpl.java ) and its Job of the AMImpl.java
to perform the business logic and return the result back to to controller .
To enforce the coding standard of MVC design pattern we have these java files EO , VO , AM , CO . with more practice you will understand the various
methods defined in each of these java files .
As usual , Thank you so much Keerthi.
This is really helpful for me .