Extensions with custom EO and VO

Question

The requirement I have is to add columns of a custom table into oracle seeded page(LeadCrtePG) and have those columns of the custom table get updated to the db when the apply is clicked on the seeded oracle page.
I created a custom EO and a VO using the EO. Created a CO extending the base page LeadCrtePG's LeadCrteCO. Since the VO is not part of the AM, I have the following code in the CO:
super.processRequest(pageContext, webBean);
OAApplicationModule am = pageContext.getApplicationModule(webBean) ;
OAViewObject vo= (OAViewObject)am.findViewObject("PelNewAsSalesLeadExtVO");
HashMap hashmap = (HashMap)am.invokeMethod("getLeadInfo");
String salesLeadId = null;
if(hashmap != null)
salesLeadId = (String)hashmap.get("SalesLeadId");
if ( vo != null )
System.out.println("Found VO PelNewAsSalesLeadExtVO for AM. Re-entered the page" );
else
System.out.println("cannot find VO PelNewAsSalesLeadExtVO" );
vo = (OAViewObject)am.createViewObject("PelNewAsSalesLeadExtVO", "pella.oracle.apps.asn.lead.server.PelNewAsSalesLeadExtVO") ;
try{
vo.executeQuery();
Row row = vo.createRow();
row.setAttribute("LeadId",salesLeadId); //LeadId is the primary key
vo.insertRow(row);
row.setNewRowState(Row.STATUS_INITIALIZED);
}catch( Exception e)
throw new OAException(e.getMessage(), OAException.INFORMATION);
A row is getting created in the VO. I checked by printing out the values in the VO in processFormRequest. But when the apply button in the page is clicked, the values are not getting saved to the table. But the values related to the seeded page are getting saved to the oracle table. So which means there is a commit in the oracle code somewhere which should also commit the custom VO changes, but that is not happening. If I do an explicit commit in processFormRequest, it errors out with some seeded page related error messages. I have even checked my mappings in the VO. I'm not sure how to solve this.
Does anyone have any suggestion on this or is there a better way to approach this requirement ?.
Thanks,
Lavanya

Answer 1

Thanks Ajay and Reetesh for the reply. I was able to figure out the mistake I was doing. I found this when I was trying out Ajay's approach. The reason for the issue was that I started off creating a text input field using a VO using personalization, later I had changed the VO name in my code. So actually the input value was not binding to the correct VO's attribute and eventually the EO. Once I corrected that, everything started working fine.
I tried both mine and Ajay's approach and both works well.
Thanks for all your help.
Lavanya