You can make metadata customizations in an application only when you are working in the Customization Developer role. In that role, customization features are enabled in the IDE (for example, the Customization Context window), while some other features are disabled (for example, you cannot create new customizable objects and you cannot edit non-customizable objects).
A customizable application can have multiple customization layers, for example,
site. Each layer can have multiple customization layer values, but only one such layer value from each layer is applied at run time.
When you open a customizable application in the Customization Developer role, JDeveloper reads the
adf-config.xml file to determine the customization classes to use and their order of precedence. JDeveloper also reads the
CustomizationLayerValues.xml file to determine the layer values to make available in the Customization Context window.
In the Customization Context window, you are allowed to select a customization layer and a layer value. The selected layer shown in the window is called the tip layer. The changes you make while in the Customization Developer role are applied to the tip layer.
If you have more than one customization layer, the order of layers presented in the Customization Context window is the same as the order of the customization classes specified in
adf-config.xml. For example, suppose you have the following in
<adf-config xmlns="http://xmlns.oracle.com/adf/config" ...> <adf-mds-config xmlns="http://xmlns.oracle.com/adf/mds/config"> <mds-config xmlns="http://xmlns.oracle.com/mds/config" ...> <cust-config> <match path="/"> <customization-class name="oracle.model.mycompany.IndustryCC"/> <customization-class name="oracle.model.mycompany.SiteCC"/> </match> </cust-config> </mds-config> </adf-mds-config> </adf-config>
Upon launching JDeveloper in the Customization Developer role, the last customization class listed within the
<cust-config> element will act as the tip layer, as shown in the following illustration of the Customization Context window:
When you select another customization layer, the selected layer then becomes the new tip layer for which you want customizations to be implemented:
Layer values from multiple customization layers can be applied, in a specified order of precedence, on top of the base application metadata. The metadata displayed in the JDeveloper editors is a combination of the base application metadata and the customization layers up to and including the tip layer (according to the precedence set in
adf-config.xml), with the values specified in the Customization Context window for each layer.
For example, the following Customization Context window illustration shows that customizations in the
financial layer value of the
industry layer are applied to the base application, and then customizations in the
remoteoffices layer value of the
site layer are applied:
The customization context of a customized application is defined by the set of customization layers applied to the base definition of the application. At the bottom of the Customization Context window, the customization context changes to reflect your selection.
Copyright © 1997, 2009, Oracle. All rights reserved.false ,,,,,,,,,,,,,,,