ADF Metadata Files

Below figure demonstrates the hierarchical relationship of the XML metadata files that you might work with in a Fusion web application that uses an ADF Business Components application module as a service interface to JSF web pages

The below figure illustrates the hierarchical relationship of the XML metadata files that you might work with in a web application that uses an ADF application module as a service interface to ADF Business Components. 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 an empty binding context.
3. When a page is rendered, the binding filter asks the binding context to load a corresponding PageDef.xml for the page.
4. The binding context creates the binding container by loading the  file as referenced by the  element in the DataBindings.cpx file.
5. The adfm.xml file loads the DataBindings.cpx contents and finds the right PageDef.xml based on the  element reference to the  element.
6. The binding container's prepareModel phase prepares and refreshes all relevant executables (most are marked deferred by default).
7. An iterator binding gets executed by referencing the named method on the data control found through the data control factory named in the case of ADF Business Components in the bc4j.xcfg file.
8. The binding container also creates the bindings defined in the  section of the pagenamePageDef.xml file for the mapped web page.
9. The web page references to ADF bindings through EL using the expression #{bindings} are resolved by accessing the binding container of the page.
10. The page pulls the available data from the bindings on the binding container.

Dig more:

• http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/appendixa.htm