ADF Toystore question: no blank row in viewobject on "Add" JSP form

Question

A new thread based on Suggestions for Automatic Commit/Rollback
In the ADF Toystore application, I did not notice the blank row behavior in the user registration section like we encountered in the other thread posting (Suggestions for Automatic Commit/Rollback To test this, I created another instance of the Accounts viewobject (called it AllAccounts) inside the ToyStoreService app module and then created a JSP to list the contents of the AllAccounts viewobject. Then, I went to the registration page (which creates a blank row in the view object with a status of STATUS_INITIALIZED) and then without submitting the form, I clicked on the link that I created to view the contents of the AllAccounts view object and noticed that a blank row did not appear. What is causing a blank row to appear in our discussions in the other thread (Suggestions for Automatic Commit/Rollback but not in the ADF Toystore application? I guess somehow this row with a status of STATUS_INITIALIZED is being "removed" but I cannot find the code that does this.
Steve -- any ideas?

Answer 1

I was trying to figure out what would be the best practice to implement 'partial rollback'. Could not really find the example in Toy Store demo. For example if we create new account, the model will get dirty. And let's say user does NOT commit the record but rather uses link and navigates to some other pages. After some work user may commit the transaction which in turn will commit blank entry in account table. Well for the sake of example let's assume that this is possible scenario.
So what I am up to is how to implement 'cancel' operation when user changes his/her mind and does something else rather then commit/save_changes in new/edit screens? What would be the best practice?
What I have done so far is rather too bulky. I have implemented event handler for all my links and cancel button in data page:
   * "Cancel" Event Handler.
   * @param ctx The DataAction context
  public void onCancel(DataActionContext ctx) {
    HttpServletRequest request = ctx.getHttpServletRequest();
    BindingContext bcc = HttpBindingContext.getContext(request);
    DCBindingContainer dbc = DCUtil.findBindingContainer(bcc, "modifyAddSchedulingUIModel");   
    DCIteratorBinding studentCat = dbc.getIteratorBinding("AddModifyScheduleView1",null , "AddModifyScheduleView1Iterator");
    Row currentRow = studentCat.getNavigatableRowIterator().getCurrentRow();   
    currentRow.refresh(Row.REFRESH_REMOVE_NEW_ROWS | Row.REFRESH_WITH_DB_FORGET_CHANGES);
    dbc.getApplicationModule().getTransaction().commit();
    String target = "individual";
    ctx.setActionForward(target);
  Any other idea?