Pagedef Editor bug - for nested appmodule

Question

Creating a nested iterator for a nested appmodule produces:
<iterator Binds="Root.SAppModule.SView"
DataControl="ControlAppModuleDataControl" RangeSize="-1"
id="SVewIterator1"/>
If a table binding is then created it shows the control binding as :
ControlAppModuleDataControl.Root.SAppModule.SView
And none of the attributes of the view are shown. Editing the page def from the page def editor changes the iterator binding to :
<iterator Binds="ControlAppModuleDataControl"
DataControl="ControlAppModuleDataControl" RangeSize="-1"
id="SVewIterator1"/>
Using the names below can someone respond with the correct settings for 11g so we can manually edit pagedef files with the correct names and should the word "Root" be included as this word was used in the 10.1.3.3 version??
root datacontrol = ControlAppModuleDataControl;
nested AppModule = SAppModule;
view name for table = SView;
thanks in advance

Answer 1

Are you getting this iterator created for you in a new page while dropping the view object from the nested AM instance in the root datacontrol AM from the data control palette?
Or are you creating iterator bindings using the structure window?
Please see section "10.3.7 How Nested Application Modules Appear in the Data Control Palette" of the ADF Developer's Guide for Forms/4GL Developers on the ADF Learning Center at http://www.oracle.com/technology/products/adf/learnadf.html for more information on this.