The ADF Faces Rich Client component set is a collection of Ajax enabled JavaServer Faces components that make development of interactive web applications as easy as drag and drop. Though as much as we want it and as much as it is our mission to make development easy, not everything can be exposed to developers in a drag and drop gesture. Sometimes a bit of Java programming and know how is required to unleash the real power of ADF Faces RC components, and this is what this section of the ADF Code Corner is about. The primary focus for the examples is set to the Fusion Development platform that includes ADF Business components as the persistence layer, ADF for the binding, ADFc as the controller and ADF Faces RC as the view layer.

In addition to the technologies just mentioned, service integration with SOA services also falls within this scope. As much as possible though I'll try to simplify the demonstrated testcase and reduce calls to web services to POJO equivalents to ensure that the provided sample workspaces run in a stand alone environment with no strings attached that would require a bigger installation of the Fusion Middleware software.

The data control and the binding layer are the key components in the Oracle Application Development Framework (ADF) architecture. Within the Fusion Development stack, the binding layer allows application developers to declaratively build data bound ADF Faces user interfaces for their Java EE web applications. The UI component 's business service binding is defined in a meta data file, the pagedef.xml file, which is created for each ADF Faces and JavaServer Faces page within a Fusion web application. To bind UI components to business services, which are the physical implementation of the business logic, ADF uses data controls which are implementation specific adapters that expose business attributes and methods in a defined and consistent way. ADF data controls exist for a variety of business services, including EJB 3.0, ADF Business Components, Web Services, BPEL, BAM and POJO. The ADF separation of the UI binding layer from the physical implementation of the business service and the business service technology allows development teams to separate their duties into business service developers and UI application developers. This section provides hints and tips for working with the ADF binding and data control layer.

A brief summary of practical security is that everyone has it on their list but not many know how to do it right. There are many facets of applied security in web applications and the implementation always is a reflection of the chosen web architecture and business requirements that the application runs in. The limiting factor for application security not necessarily is the application developer 's skill set, because just too often its the limitation in the available tools exposed by the Java EE platform or the incompatibility of security solutions in shop for different technologies like the mix and match of SOA with traditional web. The ADF code corner security workshop is an assembly of blog style how-to documents that explain application security by example for the Oracle Fusion Development platform, with a preference set to the ADF Security framework, which is an integrated part of the ADF Fusion development architecture.