Developer Tools
JDeveloper
In the example, you have customized the model view object OrderItemsView by adding the ProductName attribute from the ProductsBase entity object.
The OrdersItemsView view object now contains attributes from both the OrderItems entity object and the ProductsBase entity object. Notice that OrderItemsView now contains two ProductId attributes: ProductId from the OrderItems entity object and ProductId1 from the ProductsBase entity object; this is necessary to specify the join between the two entity objects.
When you make customizations to the model layer in an application, JDeveloper creates an XML source file using the file name of the model object you are editing. For example, the file name of OrderItemsView is
OrderItemsView.xml; the customization XML document is
OrderItemsView.xml.xml.
JDeveloper stores model layer customization documents in the
mdssys/cust package in the
Model project. If the model objects are in a package, then the
mdssys package name is prefixed with the same package name as the model objects, for example,
oracle.model.mdssys. Each customization document is created in its own customization layer value package. For example, when you are implementing customizations in the
site/remoteoffices context,
OrderItemsView.xml.xml is created in the
oracle.model.mdssys/cust/site/remoteoffices package, as shown in the following Application Navigator illustration:
To see the contents of a customization document, double-click the XML file. For example in
OrderItemsView.xml.xml, you see metadata elements such as
<mds:customization>,
<mds:insert> and
<mds:modify>.
Copyright © 1997, 2009, Oracle. All rights reserved.