Retain the entityState and postState of entities even after calling commit

Question

Dear all,
I am using view objects based on programmatic entity objects in my application for which data is populated from an array using populateRow().
I need to update the newly created/updated/deleted rows in this EO into the database using a stored procedure.
The stored procedure needs the input as an array of only those records that are created/updated/deleted with indicators of whether each row in the array is inserted/updated/deleted.
I have exposed a client interface method in the view object Impl class that calls the dbTransaction().commit() first and then calls the stored procedure.
In the doDML(), I am constructing the array and keeping the values in a page flow scope which is then accessed in the voImpl method.
In case if an exception occurs in the business logic inside the stored procedure, the data will not get posted in the database and the exception is displayed to the user in the UI.
After calling the stored procedure, I am clearing the page flow scope irrespective of whether the data has been posted to DB or not.
Consider the scenario,
I have updated 2 records. Of these, I've updated one of the records with wrong values. As per my logic, on calling the save method, doDML() will construct the data array for these two records.
Inside the stored procedure, the wrongly updated row is identified and exception is raised and the data will not get posted in the database.
Now, on getting the exception, I update the worngly updated record with proper value.
On calling the save method again, my doDML() is constucting the array with the currently updated record alone. But actually I need all the records (2 records in this case) that were modified.
My understanding is, since I've called the commit() action, all the records that make my transaction dirty gets updated as status_unmodified subsequently.
Hence, on calling commit the second time, only one record will be in modified state and that record alone is getting constructed in the array.
If I am correct,
1. Is there any way to make all those records with their status as they were before calling the commit.
2. Should I construct my array in some other method instead of doing it in doDML().
Thanks in advance.

Answer 1

You may want to try calling setClearCacheOnRollback(false) and rollback instead when you get the exception from the stored procedure. I still haven't understood where the commit is done...
You may want to consider using an Application Module variable to store your list if this helps.
Cheers,
Nick