ADF: query on pageLoad

Question

Hi,
I am new to ADF and I am struggling with this problem. Any help is greatly appreciated.
Here is the situation:
Page A - has an af:table bound to a database table. This page has a create new button and an edit button bound to a table selectOne command button.
Both these buttons navigate to Page B which should add a new row or update an existing row.
Clicking the add button on page A, navigates to page B with all form controls input enabled. User fills in the controls, clicks save and data is persisted to the database.
Clicking the edit button on Page A (with a table row selected), puts the id property of the row in the request attributes. The idea is to read this attribute from Page B and invoke a named query through a session facade and populate the page input controls.
I have implemented the create use case. but I am having trouble with the edit use case. Specifically, I am not sure how to populate the same controls by querying them. Dropping a query on the page, binds the controls to a different set of controls.
Could anyone point me in the right direction? I am using Jdev 10.1.3.2 with toplink essentials.
Thanks in advance.

Answer 1

Thanks Frank. Your response pointed me to a solution. I guess I have to point out that I am trying to both add and update using a single input form. This may not have been clear from my previous post.
Here is what I am doing: In page 1, I have a setActionListener on the edit button that sets a sessionScope.pkAttr value to row.pkAttr.
In page 2, I have one invokeAction that is bound to the findBypkAttr method, which uses the sessionScope.pkAttr through a page parameter. This method is bound to a set of attributes that display the data fetched.
In page 2, I have one more invokeAction that is bound to the constructor of the object that I am trying to add. This method is bound to a set of attributes that are empty and are rendered only when the pkAttr is null.
This way, I have two sets of controls on my form, one for add and one for update. Depending on whether the page param (defined in the pageDef.xml) is populated or not, one set is rendered.
Is there a better (cleaner) way of achieving the net outcome of being able to add and update from the same interface?