ADF Pagedefinition file contains all defines the binding variable needed of a JSF page. Whenever user drags a component from ‘Data Control’ palate to a JSF page, a page definition file will get created with the name <PAGENAME>PageDef.xml. By default, the file resides under the package view.pageDefs of your viewController. Suppose if a JSF page is created under a different directory then the page definition file also sits under a directory with the same name. The conclusion is, for each JSF page there is a page definition file, but the question is how the ADF knows which page def file belongs to the JSF page? It finds out by Databindings.cpx file. This DataBindings.Cpx file contains the mapping between JSF page and page definition file.
Note: When you delete an ADF Page Definition file / JSF, Always do Right Click on the file >> Refactor >> Delete
The below image explains about the relation between JSF file, page definition file, and Databinding.
Let’s create an ADF PageDefinition File and data binding file in an ADF project.
HR Schema (Ships with Oracle Database)
EmployeeVO object (Click here for the instruction to create Entity object from Employee table)
ADF Pagedefinition Example:
I had an ADF Fusion web application and created EmployeeEO object as shown below.
Create a JSF file: Right click on the ViewController >> Click New >> Select Page >> Input index.jsf >> Click ok
Create a Input Text Field: Expand the DataControls >> Expand AppModuleDataControl >> Expand EmployeesView >> Drag and drop a field to the JSF page >> Select Text >> Select ADF Input Text
What happens here? : ADF created a page definition file (indexPageDef.xml) and data bindings file (DataBindings.cpx) if not already exist
Let’s Open What Page Definition file contains: Double click on the indexPageDef.Xml file. The binding first name attribute is mapped to the EmployeeView object through an iterator as shown below.
Let’s open what DataBinding.xml contains: Double click on the DataBindings.xml file >> The JSF file is mapped to the Page Definition file through an ID attribute. It also tells which Data Control is used.
The views expressed on this blog are my personal views and do not necessarily reflect the views of my employer.
Please feeling free to reach me on any comments and feedbacks you have. Would be more than glad to listen and reply 🙂
Latest posts by Govind (see all)
- Primavera Error: The database is not setup to use the authentication mode selected: WebSSO:LDAP - June 22, 2017
- Primavera P6 professional Login alert box:The database has not been configured to run background jobs. To correct this error contact your system administrator - June 22, 2017
- How to integrate Oracle BI Publisher and LDAP in WebLogic server - June 21, 2017