|
ADF Designtime | ||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
AttributeInfo | |
DataControlFactory | This interface need to be implemented to support automatic creation of data controls dependin on the node type. |
DataControlListener | Listener interface used to notify when the set of data controls has changed. |
DataControlProjectConfigurer | |
DataControlProvider | The Data Control Provider is used to register new types of Data Controls. |
MethodInfo | |
RowsetInfo | Interface for accessing the set of AttributeInfo and MethodInfo objects for a given model object. |
Class Summary | |
DataControlFactoryManager | The DataControlFactoryManager handles registration of DataControlFactory classes. |
DataControlFactoryMenuListener | internal class, do not use. |
DataControlManager | Main class for registering listeners or providers. |
The ADF desing-time API allows for extension of the ADF design-time interfaces. There are a number of topics that are desigend into this framework. These topics are covered as part of this package documentation.
A registered data control provider is used to add a set of Data Controls to the Data
Control Palette. Once the provider is registerted with the DataControlManager
, the provider will provide the set of Data Controls to be populated in the Data Control Palette.
Registering a provider is done by using the following call to DataControlManager
.
DataControlManager.getInstance().addControlProvider(new DCXDataControlProvider());
A provider implements the DataControlProvider
interface.
It is not required that Data Controls exist as nodes in a project. A provider
may query some external resource in order to obtain a list of registered Data
Controls.
A DataControlFactory
is responsible for creating a Data
Control Definition and registering it with a particular provider. We have Data
Control Factories for Java Bean, EJB, Web Service and Toplink Java Beans. Most
of these factories derive from the Java Bean factory class DCFactoryGeneric
.
After they create a Data Control definition they register it in a .DCX file.
The contents of the .DCX file are then read by the DCX Data Control Provider
(oracle.adf.dt.providers.DCXDataControlProvider) and used to populate
the Data Control Palette.
A {@see oracle.adf.dt.dbpanel.DataBindingPanelListener} is associated with a particular JDeveloper node type. There can only be one Data Binding Panel listener per document type. We have registered the following listeners:
Listener | Document Type |
---|---|
oracle.adf.dt.dbpanel.jclient.JClientXMLListener | All .java files opened in the UIEditor |
oracle.adf.dt.dbpanel.uix.UIXBindingPanelListener | All instances of oracle.cabo.ide.addin.UIXSourceNode |
oracle.adf.dt.dbpanel.xmllistener.XmlBasedBindingPanelListener | All .jsp and .jspx pages. This handles Struts and non-Struts scenarios. |
oracle.adfimpl.struts.ui.dbpanel.StrutsBindingPanelListener | All instances of oracle.adfimpl.struts.AppContext |
oracle.adf.dt.dbpanel.jrad.JRadBindingPanelListener | All instances of oracle.adf.mds.dt.ui.ide.model.MDSDocumentNode |
The Data Binding Panel listener is responsible for populating the Data Control Palette's control type list. Once a selection is made, the listener then provides the Transferable object ot be used in populating the document with the content that refers to the created binding(s). The Data Binding Panel listnener interacts with the {@see oracle.adf.dt.dbpanel.DataBindingManager} to create control bindings. The Data Binding Manager provides the following method to create control bindings:
public JUDTControlBinding createControlBinding(String sBindingTypeName, oracle.adf.dt.controls.DataControlTreeNode treeNode)
The .DataControlTreeNode parameter is obtained from the Data Binding Panel and passed into the above function. The sBindingTypeName parameter is a logical binding type passed to the Data Binding Manager. This logical type is interpreted by the active oracle.adf.dt.objects.ControlBindingFactory the factory creates the control binding instance and returns it the the Data Binding Panel Listener. In addition to creating the specified binding, the Data Binding Manager is responsible for creating the binding container and any necessary iterator bindings required by the selected tree node. The iterator defaults are controlled by the selected tree node.
|
ADF Designtime | ||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
Copyright © 1997, 2004, Oracle. All rights reserved.