A.3 ADF File Syntax Diagram

Figure A-2 illustrates the hierarchical relationship of the XML metadata files that you may work with in the web application that uses an EJB session bean as a service interface to JavaBeans. At runtime, the objects created from these files interact in this sequence:

1. When the first request for an ADF databound web page occurs, the servlet registers the Oracle ADF servlet filter ADFBindingFilter named in the web.xml file.

2. The binding filter creates a binding context by reading the CpxFileName init param from the web.xml file.

3. The binding context creates the binding container by loading the <pagename>PageDef.xml file as referenced by the <pagemap> element from the DataBindings.cpx file.

4. The binding container's prepareModel phase prepares/refreshes all the executables.

5. An iterator bindings gets executed in by referencing the named method on the session bean facade specified by the data control factory named in the DataControls.dcx file.

6. The binding container also creates the bindings defined in the <bindings> section of the <pagename>PageDef.xml file for the mapped web page.

7. The web page references to ADF bindings through EL using the expression #{bindings} get resolved by accessing the binding container of the page.

8. The page pulls the available data from the bindings on the binding container.

Figure A-2 Oracle ADF File Hierarchy and Syntax Diagram for an EJB-based Web Application