You do not need to edit your application code to change the data model
definition it will use to connect to your business services data source.
The definition is contained entirely in the meta-data for the JClient
project in two files: DataBindings.cpx and UIModel.xml
.
You might want to do this because you had been using a local configuration to test your application in JDeveloper and you now want to change to a data model definition that uses a remote deployment configuration. You could also decide to use an entirely different data model defined in a different business service project. Again, no code changes are required to accomplish this task.
To reference the new client data model definition in the JClient meta-data:
Add a new client data model
definition to the DataBindings.cpx file in your
JClient project and remember the name you chose (for example,
remotedatamodel).
Note: If you change your data model to use an ADF
Business Components application module from a package in a different
project and the new application module is defined as Session Bean
(BMT), then you must modify the <ejb-ref> entry
in the web.xml file as well as update the .cpx
file.
Optionally, you can open the DataBindings.cpx file in
the XML editor and edit the attributes of the AppModuleDataControl:
Open the UIModel.xml file in the XML editor, display
the Structure window and select any binding that references the old
data control.
With the binding selected in the Structure window, open the Property Inspector and edit the Model Reference attribute so it names the new data model definition. Repeat for each binding in the binding definition.
Repeat for each panel or form in your JClient project so their own binding definitions have the same changes.
About the Client Project Configuration
About the Frame and Applet Class in JClient
About the Layout Panel in JClient
Creating a Client Data Model Definition for JClient Forms
Copyright © 1997, 2004, Oracle. All rights reserved.