ADF Master Detail Insertion and updation

Question

Dear All
I am developing a web application with the ADF using ADF BC4J as a buisness service and JSP as th view.
I am creating a Master detail page that makes the user add the ,master and the detail(s) information in the same page.
Example:
you may insert the department and the employess in that department in the same transaction (post) also the update

Answer 1

Two questions...
1. Will a future version of Jdeveloper support a drag and drop update-able multirow table?
2. The existing example of doing this (Without Jheadstart) behaves different than a single row input form, as Duncan Mills points out, in that it loses the values that are input if validation errors occur. This same thing happends in the JHeadstart workspace.
a) after running the code and just showing the bindings and form values, it appears a standard input form has the new values immediately after processUpdateModel(). Even if they are in error, and it later fails to make it through validateModelUpdates the values are retained.
b) in the Multi-row example, you can examine the form bean values (for the multiple rows), and examine the values from the rowset obtained through the DCUtil.findSpelObject() and JUCtrlValueBindingRef calls, and the bindings don't change. The validateModelUpdates still manages to produce the error though.
So, with a multi-row update form...
a) How do you get the ROW specific error msg generated from a declarative or method-based validator? - that is, put a msg in for the row like: You can't put XXX into this field.
Right now, we modified the BEAN to include an ErrMsg column and added that as a transient attribute to entity and view, and can display the messages via that by putting them in during the processUpdateModel(). Of course, most of the validation ended up in the processUpdateModel(), with none in the Entity.
b) Where are those values going if they are placed into the bindings as they can't be examined later after processUpdateModel?
Here's a method stub that we used to show values...
   * showFormValues retrieves the array of form beans as well as the
   * EmployeesView1.rangeSet, and displays the form values for Salary
   * and CommissionPct against the JUCtrlValueBindingRef (row-based)
   * bindings from EmployeesView1
   * @param actionContext
  private void showFormValues( DataActionContext actionContext )
      DynaActionForm  updateForm = (DynaActionForm) actionContext.getActionForm();
      UpdateRowBean[] updatedRows = (UpdateRowBean[])updateForm.get("Row");
      System.out.println("********** showFormValues **********");
      java.util.List origRows =
        (java.util.List) DCUtil.findSpelObject(actionContext.getBindingContainer()
                                             , "EmployeesView1.rangeSet");
      // Now loop through the bean array
      for (int i = 0; i < origRows.size(); i++)
         //Get the rowKey of the submitted updated Row 
         String theRowKey = updatedRows.getRowKeyStr();
//Get the corresponding row from the origional set
JUCtrlValueBindingRef oldRow = (JUCtrlValueBindingRef)origRows.get(i);
//Check the update row needs processing and matches the source row
if (oldRow.get(JUCtrlValueBindingRef.RANGESET_ROW_KEY_STR).equals(theRowKey))
// Form value - does not appear to change
System.out.print( i + ": sal=" + updatedRows[i].getSalary() +
", comm=" + updatedRows[i].getCommissionPct() );
System.out.println("....Salary=" + oldRow.get("Salary") +
", CommissionPct=" + oldRow.get("CommissionPct") );
} // match on rowKeyStr
} // for i
System.out.println("************************************");
} // showFormValues