It does not create a user interface, but is a PURE encapsulation of business logic that communicates with a separate CLIENT application, which HANDLES user interaction.

The advantage of ADF BC over UI-enforced business logic is reusability.

By maintaining a cache of data in memory, ADF BC reduces the number of database trips required by an application resulting in improved performance and scalability.

Removing the business logic out of the database keeps the database from HANDLING anything but data, which increases an application's modularity and efficiency.

Entity objects, view objects, and application modules each have two parts: a Java class file and an XML file. The files have different purposes. ADF BC is a framework, this means that much of its functionality is contained in a set of libraries. ADF BC classes extend (subclass) the base classes provided by these libraries to provide complex business logic, which REQUIRES the procedural power of Java to implement.

It does not create a user interface, but is a pure encapsulation of business logic that communicates with a separate client application, which handles user interaction.

The advantage of ADF BC over UI-enforced business logic is reusability.

By maintaining a cache of data in memory, ADF BC reduces the number of database trips required by an application resulting in improved performance and scalability.

Removing the business logic out of the database keeps the database from handling anything but data, which increases an application's modularity and efficiency.

Entity objects, view objects, and application modules each have two parts: a Java class file and an XML file. The files have different purposes. ADF BC is a framework, this means that much of its functionality is contained in a set of libraries. ADF BC classes extend (subclass) the base classes provided by these libraries to provide complex business logic, which requires the procedural power of Java to implement.