How ADF implements MVC

Oracle ADF extends the MVC architecture by introducing a generic binding layer as the model.
In Oracle ADF, the architecture you use to build Java EE applications is comprised of the view
layer (typically represented by ADF Faces), the controller layer (ADF controller), the model
layer (represented by ADF data controls and page data bindings), and the business service layer
(often ADF Business Components though EJB, web services, POJOs, and more are possible).
Following are the ADF components:
‹ ADF Business Components: A business service based on a relational database
table schema that, before persisting user data entries, enforces business logic
and validation rules.
‹ ADF Model: This data binding layer is an abstraction layer that facilitates access
to data from underlying business service layers. This layer acts as an interface
that exposes the services available from the business service layers to the UI
components. This helps the declarative binding of the UI components with the
exposed services.
‹ ADF Task flows: The ADF controller extends the JSF navigation handler for page
navigation and UI component event handling. ADF Task flow is a concept of the
ADF controller, that allows you to build reusable navigation units that you can
use standalone or chain up to an overall application flow.
‹ ADF Faces: This is a JSF-based and Ajax-enabled component set, that provides a
rich set of user interface components for building the application's user interface.