Create, commit, rollback button behavior

Question

I have a view object dropped as a form. It has the default create, commit and rollback buttons.
On initial display, only the create button is enabled, and the form is read-only.
I click create button, which then it allows me to enter input.
Upon clicking create button again, the form saves the input, clears itself, awaiting next input, and both commit and rollback buttons become enabled. I can continue to add more rows using create button.
When I click either commit or rollback, the form becomes read-only again, and only the create button is enabled.
This is the JDev standard form behavior which I want.
Now, I add just 2 more enhancement, and this behavior gets broken.
First, I drop the same view object as a table underneath the form, so that as records are added, the table will reflect it.
Secondly, the form has two selectOneChoice components whereby upon valuechange on the first selectOneChoice, the second
selectOnechoice items are dynamically populated via bean method and partial trigger.
With these 2 changes, the entire page behaves like following:
Upon create click, it gives me the form, but subsequent click on create does not clear the fields.
If I click the create again, it then clears the fields. So, it takes 2 clicks on create to get a cleared form.
But, it adds the row because I see it in the table below, but only one column displays the value in the newly added row.
Upon commit, the row displays all values.
Another thing is it fails to save the value from the second selectOneChoice field.
Could you please point out what I am not doing right here?
I would appreciate your insight.
Thanks.
Edited by: paikyunki on Oct 23, 2008 6:31 PM

Answer 1

Chris,
I might post the code tomorrow in my office - I am home now. Thanks for your offer.
I gave some thoughts to my problem later, and it seems like one easy way out would be to create a form using ADF Faces components, then write a service method to insert a new row
from the data gleaned through this form.
I am new to JDev, and this approach of not utilizing the built-in functions of JDev may seem like defeating the very purpose of JDev.
I find Oracle's Business Component's non-gui model very understandable and a strong alternative to Hibernate/Spring.
However, it seems like sometimes it just may be easier, such as in this case, to resort to programmatic way.
What is your view on this? I have used JDev less than 3 wks and would like to hear from experts.
Yunki