Oracle® Application Development Framework Developer's Guide For Forms/4GL Developers 10g (10.1.3.1.0) Part Number B25947-01 |
|
|
View PDF |
The relationship between the Oracle ADF metadata files defines dependencies between the model data and the user interface projects. The dependencies are defined as file references within XML elements of the files.
Figure A-1 illustrates the hierarchical relationship of the XML metadata files that you may work with in the Oracle ADF application that uses an ADF Business Components application module as a service interface to JSF web pages.
In an ADF Business Components application, the data control implementation files are contained within the application. The application module and view object XML component descriptor files provide the references for the data control. These files, in conjunction with the bc4j.xcfg
file (see Section A.4) provide the necessary information for the data control.
A workspace that uses ADF Business Components in one project and a non-ADF Business Components data control in another project, like the SRDemoFAQ data control, may have a DataControls.dcx
file, as well as supporting <sessionbeanname>
.xml
and <beanname>
.xml
files. For more information on the non-ADF Business Components data controls, see the Oracle Application Development Framework Developers Guide 10g for J2EE Developers.
These standard XML configuration files for an Oracle ADF application appear in your user interface project:
DataBindings.cpx
— This file contains the pageMap, page definitions references, and data control references. The file is created the first time you create a data binding for a UI component (either from the Structure window or from the Data Control Palette). The DataBindings.cpx
file defines the Oracle ADF binding context for the entire application. The binding context provides access to the bindings across the entire application. The DataBindings.cpx
file also contains references to the <pagename>
PageDef.xml
files that define the metadata for the Oracle ADF bindings in each web page.
See Appendix A, "DataBindings.cpx" for details about what you can configure in the DataBindings.cpx
file.
<pagename>
PageDef.xml
—This is the page definition XML file. This file is created each time you design a new web page using the Data Control Palette or Structure window. These XML files contain the metadata used to create the bindings that populate the data in the web page's UI components. For every web page that refers to an ADF binding, there must be a corresponding page definition file with binding definitions.
See Appendix A, "<pageName>PageDef.xml" for details about what you can configure in the <pagename>
PageDef.xml
file.
These XML configuration files required in a JSF application appear in your user interface project:
web.xml
—Part of the application's configuration is determined by the contents of its J2EE application deployment descriptor, web.xml
. The web.xml
file defines everything about your application that a server needs to know. The file plays a role in configuring the Oracle ADF data binding by setting up the ADFBindingFilter. Additional runtime settings include servlet runtime and initialization parameters, custom tag library location, and security settings.
For details about ADF data binding and JSF configuration options, see Appendix A, "web.xml".
faces-config.xml
—This JSF configuration file lets you register a JSF application's resources, such as validators, converters, managed beans, and navigation rules. While an application can have more than one configuration resource file, and that file can have any name, typically the filename is faces-config.xml
.
For details about JSF configuration options, see Appendix A, "faces-config.xml".
adf-faces-config.xml
—This ADF Faces configuration file lets you configure ADF Faces-specific user interface features such as accessibility levels, custom skins, enhanced debugging, and right-to-left page rendering.
For details about ADF Faces configuration options, see Appendix A, "adf-faces-config.xml".