ADF BC/Struts/JSP

Question

I'm hoping some of you out there can just confirm some of my observations and maybe answer a few high level questions.
I have been playing around with Jdev 9052 for a few days, I've read Steve Muench's Data Binding primer and have even created a few demo apps.
The one i'm currently playing with has two data pages, a browse form and an edit form. The browse form simply displays a few rows from a view object, has an edit and a delete link for each row, and has a create link outside the main table for creating a new row.
To make the create link work, i have a binding on the BrowseForm data page(called "Create") bound to the Create action on my literator. I also have a forward on my BrowseForm data page called "Create" that forwards to my EditForm data page. The edit page then displays the new blank row, I fill in the data and press the submit button.
The data action automatically copies the data into the new blank row in the view object. The submit button's name is "event_save" and i have an onSave method defined in the pages DataAction that commits the transaction.
My questions are:
A) Is this the correct way to be doing this?
B) Assuming this is the correct way, is the BC framework holding a database transaction open between the time the Create action is executed on the iterator(in response to clicking the "New" link) and the commit operation is executed(in response to the submit button on the edit page)???
C) If it is holding open a transaction during the data entry, isn't that a bad thing in a web application?
D) If it is holding open a transaction, what does the BC framework do when the app module pool gets full and it needs to start recycling modules?
I have one more question not related to my example. In every web application I have written for use by the general public, and in every app I have used that was written for the public, there has never been any concept of having to Commit changes separate from submitting the data to the server. As a user when i press the submit button I expect the data to be saved, i don't expect to also have to click on a Commit button like I do in Oracle Forms. My question is, does Oracle have any plans to add any features to ADF BC to make this kind of development any easier and more declarative?

Answer 1

Sorry I haven't been able to reply, got dragged into an emergency project.
I have it all working very well, and I really should have figured the commit thing out myself, I was just thinking about it way too hard.
I do have one more quick question about something I was able to do, I want to have a link next to each row that will delete that row. In order to do that I need to:
1) Set the current row
2) Delete the row
3) Commit
I was able to do this declarative without having to create any extra data actions by passing three event params on a link such as the following
<a href="engineManagement.do?event=selectRow&rowKeyStr=<c:out value='${Row.rowKeyStr}' />&event=Delete&event=Commit" >Delete</a>
(selectRow is bound to the setCurrentRowWithKey method)
Should I be using the event system in this way?
This seems to work very well, but i'm concerned about the ordering of the events, if they get executed in the wrong order, the wrong row will be deleted or the transaction won't get committed. Will the ADF controller always execute events in the order they appear on the query string?