This content has been marked as final. Show 8 replies
Below should work from Controller.
import oracle.jbo.RowSetIterator; ... OAApplicationModule am = pageContext.getApplicationModule(webBean); oracle.jbo.ViewObject spupdateVo=am.findViewObject("SpecialInformationUpdateVO1"); RowSetIterator tblvorow= spupdateVo.createRowSetIterator("sptblVoRow");
Edited by: appsjit on Nov 10, 2012 9:24 PM
Edited by: appsjit on Nov 12, 2012 7:59 AM
Hi Jyothi ,
Could you please tell us what exactly is the error you are getting in line 3 , also ensure that your new nested region
is inside the page layout and you have to attached VO to that .
Edited by: keerthioaf on Nov 11, 2012 10:27 AM
To create a row set iterator, use below line of code instead of your line number 3.
OAApplicationModule rootAm=pageContext.getRootApplicationModule(); oracle.jbo.ViewObject spupdateVo=rootAm.findViewObject("SpecialInformationUpdateVO1"); RowSetIterator iter = spupdateVo.createRowSetIterator("iter"); iter.setRangeStart(0); iter.setRangeSize(spupdateVo.getFetchedRowCount)
Thanks for your replies.
I tried these methods earlier but was not working.
The problem i am facing is i am not able to create a RowSetIterator for VO.
Gyan, i tried your code also, it is failing at the step RowSetIterator.
The error i am getting is
At erroring line 97 i am creating RowSetIterator.
I attached the region by personalization with in the pagelayout only and i have attached custom AM also to this custom region.
Jyothi,1 person found this helpful
It's throwing null pointer exception becoz you have attached the VO to the custom AM. And this custom AM is attached to the Custom Region.
But in the code you are trying to find the spupdateVo in Root AM.
Yes, that is wat happening now.
So you are saying it is not possible to call seeded AM to custom region CO.
Then i think i have to extend the seeded AM and add my VO right?
Pls give ur suggestions
I think you need to extend the controller at the pageLayout Region which would have access to all the regions and also their corresponding AMs.
Its very much possible to get the handle of the custom AM from ur custom CO.
You need to change a line of code.
//Replace customGroupAM with the name of ur custom AM.
CustomGroupAM am = (CustomGroupAM)pageContext.getApplicationModule(webBean);