Refresh view layer based on changes in AppmoduleImpl Method

Question

Hi,
Version of Jdev :Studio Edition Version 11.1.2.3.0
Use Case: Fields on screen cant be based on a entity as there is just too much calculation in backend procedures for doing some validations of data that involves various tables ,and then fields from various
tables are shown ,so now to handle this i created a view object (a programmatic view object) ,so now i have added these fields on jsf page.
I have few functions there in AppModuleImpl where I am calling setters of this programmatic view ,and calling these functions from managed bean using AdfUtils, though as per my debugging
it seems values are set by setter but screen is not refreshing.
public void populateData() {
System.out.println("Inside populate Data");
ViewObject ctm = this.getMasterType1();
System.out.println("Inside populate Data1");
//ScreenRowImpl r1;
ViewObject screen = this.getScreen();
System.out.println("Inside populate Data2");
MasterTypeROVORowImpl r = (MasterTypeROVORowImpl)ctm.getCurrentRow();
System.out.println("Inside populate Data3 " + screen.getRowCount());
// if (screen.getRowCount() == 0) {
ScreenRowImpl r1 = (ScreenRowImpl)screen.createRow();
System.out.println("Inside populate Data4 " + r.getText());
String s1 = r.getText();
System.out.println("populating1111");
r1.setTEXT(s1);
System.out.println("populating");
screen.executeQuery();
I see all the system out messages but screen is not refreshing ,I am calling this as part of method call activity in a bounded taskflow ....
Can anyone tell me what I m missing or my approach is correct or not ....or it can be done in a simpler way.
Actually i m a forms developer ,creating a oracle form in ADF ...this oracle form used to be based on a control block ......
Regards,
NewBie....
Edited by: user12209214 on May 19, 2013 12:16 AM

Answer 1

That you see you're prints only means that your method outta called. The code creates a new row, but never inserts the row into the rowset. Then you call execute query which loses any connection to the new route which is not part of the rowset.
First action would never to call insertRow(r1) on the view object.
If you change data this way, only the model layer knows about it, the ui can't know about this (one of the disadvantages of using plsql or this construct you try). You have to tell the view controller to update it's data to. For this you can execute the iterator in the binding layer and/or ppr the container showing your data.
Then I don't see any complicated plsql called do I question if a programmatic co is necessary.
Timo