ActivateStateForUndo and passivateStateForUndo . We need explain.

Question

I have problem with delete record if i generate Exception.
I am analyse source of jHeadStart and discover than passivateStateForUndo work incorrect
i comment
request.setAttribute("undoId",undoId);
this line , my web application work correct
protected void passivateStateForUndo(DataActionContext daContext)
mLog.debug("Executing passivateStateForUndo so we can restore deleted rows when transaction fails");
// We have created an ArrayList of rows to be deleted and at the end of the
// model update we first passivate the current state, then remove all the rows.
// We do this because when the commit fails because of some busines rules,
// we have to undo the deletion of the rows so we can display them again on
// the UIX page. We cannot do a simple rollback because then we would loose
// the changes made to other records as well. (With JSP as View this is not
// the case, because then we use Form Beans to re-display the entered values)
HttpServletRequest request = daContext.getHttpServletRequest();
DCBindingContainer container = daContext.getBindingContainer();
// get the am through commit binding
JUCtrlActionBinding ab = (JUCtrlActionBinding)container.findCtrlBinding(COMMIT);
if (ab!=null)
ApplicationModule am = ab.getDataControl().getApplicationModule();
String undoId = am.passivateStateForUndo("beforeModelUpdate", null, 0);
// container.refreshControl();
// request.setAttribute("undoId",undoId);
else
mLog.debug("Cannot passivateStateForUndo, no Commit binding found to get to the application module");
and i correct delete some records,
why?

Answer 1

activateStateForUndo and passivateStateForUndo are ADF BC functionality, which can be compared to 'middle tier savepoints'. As the inline documentation explains, it is very important that this is done to ensure correct handling of deleted rows. If we would not do that, the end user would not be able to correct his mistake if he tried to delete a row that he was not allowed to delete.
From other posts you made I know that this situation only occurs in a very specific situation for you, namely when you throw a JboException on the 'remove()' method of the EntityImpl.
Before we can investigate this further, we'll need to know which JHeadstart and JDeveloper version you are using, and a description of how we can reproduce this situation in a standard HR application.
Kind regards,
Peter Ebell
JHeadstart Team