ADF is built on top of the Java and Java EE stack. If you are familiar with Java EE, this topic is for you. Let us take a quick look at the basic building blocks of these two technologies to see what they have in common:
The ADF Architecture is targeted at providing a service-based, loosely coupled solution with the following five layers:
- View: works as the presentation layer. ADF Faces is used for this purpose. ADF Faces owns more than 150 components to support the development of complex UI.
- Controller: the navigation is handled by this layer using the ADF Task Flow. The other technology choice in this layer can be JSF Struts.
- Model: This layer is on top of the service layer and abstracts the business services exposed to the view layer. Here is where Data Controls and Data Bindings appear to be used on some other layers.
- Business Service. This layer is responsible for handling the interactions between the DB and the model layer by providing database persistence, object/relational mapping, managing transactions, and so on. Business logic also is also taken care in this layer. ADF Business Components are the first choice to develop the business service layer apart from Java, EJB, and web services.
- Metadata Services: Customization and personalization of the application is done using metadata services framework
The following diagram shows how ADF layers fit into the Model-View-Controller architecture:
Endeca Information Discovery Integrator is a powerful visual data integration environment that includes the Information Acquisition System (IAS) for gathering content from delimited files, file systems, JDBC databases, and Web sites; and out-of-the-box ETL purpose-built for incorporating data from a wide array of sources, including Oracle BI Server.
All the information about Endeca IDI: Here
As the industry begins the rapid adoption of Java EE 7, work has begun on Java EE 8. The Java community has prioritized the desired features for Java EE 8.
More details at: here