This content has been marked as final. Show 4 replies
How about using one method in a bean to call the executeWithParams and after this in the same method get the row and the attributes, store them and then continue loading the page?
Thanks Timo. This thought came to my mind but then I wasn't sure how to obtain the current row after ExecuteWithParams methodAction call.
I do not want put any data model specific code in backing bean. What I mean is that I don't want to use data model APIs to get that data.
What mechanism are you proposing to get the row after the call? I would appreciate if you could provide some reference or may be sample code.
I see two possible ways to get to the attributes. First you can get the iterator current row and get the attributes from there. Second you add attribute bindings to the methods pageDef file for all attributes you are interested in. Then you access them using the attribute binding. I never tested the 2nd method but I guess the framework will fill the attribute bindings like it does in a normal page.
Sorry, can't give you sample code on this add I'm not in front of a PC.
Thanks Pino. I used the first method of getting the iterator and then current row.
I hope this is not violating the MVC layer concept as I had to import oracle.jbo.Row, oracle.jbo.ViewObject and oracle.adf.model classes for BindingContext/Container.
Is it Okay to use these on view layer?