First page Back Continue Last page Graphics

ADF BC Implementation Architecture


Notes:

ADF BC Implementation Architecture

Before entering into a detailed discussion on each of the key components in subsequent lessons, it is helpful to understand a few guiding principles that have gone into the design and implementation of this layer of Oracle ADF:

It is based on standard Java and XML: Each component’s run-time behavior is configured in an XML file, whereas the Java source code for the framework is extensible.

It is database and application server agnostic. You can use any environment with a JVM.

It implements all the popular Java EE design patterns, such as Model/View/Controller, Interface/Implementation Separation, and Session Facade.

It organizes components into packages. To ensure that your code does not clash with reusable code from other organizations, you should choose package names that begin with your organization’s name or Web domain name.

Most of the classes and interfaces comprising the ADF BC prebuilt code are in the oracle.jbo or the oracle.jbo.server packages.

Components are metadata driven, but you can optionally generate a Java class where you can add code.