Suggestions for Automatic Commit/Rollback

Question

Consider the following scenario:
A list page displays all of the records currently stored in a table. A user clicks on a link on the list page that fires the Create event and takes them to another page for entering the details of the new record. The user decides they made a mistake and clicks their browser's Back button to abort the process. There is now a new, unpopulated record on the list page.
What is the best way to handle this situation if the user cannot be concerned with manual Commits or Rollbacks? Committing after the new record details are submitted seems okay, but rolling back every time the list page is loaded renders the First/Previous/Next/Last navigation buttons useless.
Thanks,
Ryan

Answer 1

Create Action in ADF JSP bindings is meant to create and insert a new row into collection (and if the dataControl in action is ADFBC, then it also marks the row as temporary/initialized as indicated above).
To achieve the backbutton support, for such cases in ADF apps, we recommend using a cancel operation that is bound to 'delete' Action on the iterator which 'removes' the newly created temporary row from the collection so that it's not visible in the collection at all.
Using browser back button after create action will result in the temporary new row in the collection as noted above.
This was designed as per numerous feedback on OTN for our previous JSP solution for creating new rows where a number of teams complained about duplicate row creation on a create row action. You could still achieve this as suggested above by creating a new and initialized row and then copying it's values on the form and then removing the row and then recreating another new row on submit. Note that that requires extra copying of all display values etc and in ADF we decided to avoid that route.