ADF BC with CDM Ruleframe informationals and warnings

Question

Best experts,
I have an issue regarding using ADF BC in combination with CDM-RuleFrame.
We are raising different kind of messsages (errors,warnings,informationals).
JHeadstart delivers an AM that raises the errors but ignores the transactions with warnings and informationals.
To display the informationals and warnings I want to follow this path:
DB ==> Transaction (stores the messages on the AM) ==> CommitBean (Displays the messages in browser)
I use the folowing transactionImpl:
public class RuleFrameTransactionImpl extends DBTransactionImpl2{
  String mUndoId;
  private static Logger sLog = Logger.getLogger(RuleFrameTransactionImpl.class);
  private boolean hasErrors;
  public static String MESSAGE_SEPARATOR = "<br>";
  public static String QMS_UNHANDLED_EXCEPTION = "QMS-00100";
  public RuleFrameTransactionImpl()
    super();
   * Standard Ruleframe
  private void openRuleFrameTransaction()
    try
      CallableStatement cs = this.createCallableStatement("begin qms_transaction_mgt.open_transaction('JAVA'); end;",
                                                          1);
      try
        cs.execute();
      catch (java.sql.SQLException e)
        handleSQLError(e);
      finally
        try
          cs.close();
        catch (Exception ex)
          sLog.error("Error closing Callable Statement for CDM RuleFrame Open Transaction: " + ex);
  public void closeRuleFrameTransaction()
    // Close RuleFrame transaction
    CallableStatement cs = this.createCallableStatement("begin qms_transaction_mgt.close_transaction('JAVA'); end;",
                                                        1);
    try
      cs.execute();
      setDBFeedbackOnApplicationModule();
    catch (java.sql.SQLException e)
      handleSQLError(e);
    finally
      try
        cs.close();
      catch (Exception ex)
        sLog.error("Error closing Callable Statement for CDM RuleFrame Close Transaction: " + ex);
  @Override
  public void postChanges(TransactionEvent te)
    passivateStateForUndo();
    openRuleFrameTransaction();
    super.postChanges(te);
    setDBFeedbackOnApplicationModule();
    catch (DMLException e)
      // retrieve SQL error from details
      Object details[] = e.getDetails();
      if (details[0] instanceof SQLException)
        handleSQLError((SQLException)details[0]);
      // If reached this line, the detail is not a SQLException,
      // so throw it again
      throw e;
  public void handleSQLError(SQLException e)
    throws JboException
    if ((e.toString().indexOf("ORA-20998") > 0) ||
      // 20999 is raised when posting of changes fails
      // due to database constraint violation or built-in TAPI rule
      (e.toString().indexOf("ORA-20999") > 0))
      setDBFeedbackOnApplicationModule();
    else
      // Raise the SQL exception, it is not a RuleFrame error
      throw new JboException(e);
  @Override
  public void doCommit()
    closeRuleFrameTransaction();
    super.doCommit();
  public void passivateStateForUndo()
    sLog.debug("Executing passivateStateForUndo so we can roll back the Application Module when RuleFrame transaction fails");
    ApplicationModule am = getRootApplicationModule();
    String undoId = am.passivateStateForUndo("beforeRuleFramePost",
                                             null,
                                             0);
    mUndoId = undoId;
    hasErrors = false;
  public void activateStateForUndo()
    // If an undoId is stored on the request, we rollback the transaction
    // to the undoId savepoint. The undoId is stored prior to deleteing rows
    // from a table. By rolling back to the state prior to removing the
    // rows, we can re-display the failed-to-delete rows
    String undoId = mUndoId;
    if (undoId != null)
      sLog.debug("Executing activateStateForUndo, restoring state of before postChanges because RuleFrame transaction failed");
      ApplicationModule am = getRootApplicationModule();
      am.activateStateForUndo(undoId,
                              0);
   * Aanpassingen vanwege QMS-messages (informationals + warnings)
  public void setDBFeedbackOnApplicationModule()
    RuleFrameApplicationModuleImpl am = (RuleFrameApplicationModuleImpl)getRootApplicationModule();
    sLog.debug("SetDBFeedback");
    CallableStatement st = null;
    try
      sLog.trace("create statement");
      // 1. Create a JDBC PreparedStatement for
      st = createCallableStatement("begin jhs_pck_errors.get_db_feedback(?,?,?);end;",
                                   0);
      sLog.trace("define parameters");
      // 2. Define out parameters
      st.registerOutParameter(1,
                              Types.VARCHAR);
      st.registerOutParameter(2,
                              Types.VARCHAR);
      st.registerOutParameter(3,
                              Types.VARCHAR);
      sLog.trace("Execute statement");
      // 3. Execute the statement
      st.executeUpdate();
      sLog.trace("Build return objects");
      // 4. Build return objects
      ArrayList informationArray = new ArrayList();
      ArrayList warningArray = new ArrayList();
      ArrayList errorArray = new ArrayList();
      sLog.trace("merge into array");
      mergeStringIntoArray(informationArray,
                           st.getString(1));
      mergeStringIntoArray(warningArray,
                           st.getString(2));
      mergeStringIntoArray(errorArray,
                           st.getString(3));
      if (errorArray.size() > 0)
        //Error occured ==> rollback am.
        activateStateForUndo();
      am.addErrorArray(errorArray);
      am.addWarningArray(warningArray);
      am.addInformationArray(informationArray);
    catch (SQLException e)
      throw new JboException(e);
    finally
      if (st != null)
        try
          // 5. Close the statement
          st.close();
        catch (SQLException e)
  private void mergeStringIntoArray(ArrayList al, String string)
    sLog.debug(string);
    if (string != null)
      string = string.replaceAll("   ",
                                 "°");
      StringTokenizer st = new StringTokenizer(string,
                                               "°");
      int tokenCount = st.countTokens();
      sLog.debug("Tokencount messages : " + tokenCount);
      for (int i = 0; i < tokenCount; i++)
        sLog.debug("Add " + i);
        al.add(st.nextToken());
}This works when there are only informationals or warnings.
When errors are raised I recieve the following stacktrace:
<Warning> <oracle.adf.controller.faces.lifecycle.Utils> <BEA-000000> <ADF: Adding the following JSF error message: Internal error:Entity.afterCommit.status_modified
oracle.jbo.JboException: Internal error:Entity.afterCommit.status_modified
at oracle.jbo.server.EntityImpl.afterCommit(EntityImpl.java:7049)
at oracle.jbo.server.DBTransactionImpl.doAfterCommit(DBTransactionImpl.java:2189)
at oracle.jbo.server.DBTransactionImpl.commitInternal(DBTransactionImpl.java:2085)
at oracle.jbo.server.DBTransactionImpl.commit(DBTransactionImpl.java:2273)
at local.achmeavastgoed.model.adfbc.base.RuleFrameTransactionImpl.commit(RuleFrameTransactionImpl.java:188)
Can you give me some advise?
Regards,
Romano

Answer 1

Hi Romano,
your application is not aware of the fact that there are errors because all exceptions are gracefully handled.
Because of that the doCommit() in your code example will just commit the changes by calling super.doCommit() even after the activateStateForUndo() did a rollback.
public void doCommit()
    closeRuleFrameTransaction();
    super.doCommit();
  }So you need to change two things:
First rewrite the doCommit()
public void doCommit()
    closeRuleFrameTransaction();
try{
    super.doCommit();
      } catch (JboException e){
      //  do something here
}And also throw a Jbo exception in the handleSQLError()
   public void handleSQLError(SQLException e) throws JboException
      if ((e.toString().indexOf("ORA-20998") > 0)
           // 20999 is raised when posting of changes fails
           // due to database constraint violation or built-in TAPI rule    
           || (e.toString().indexOf("ORA-20999") > 0)
         setDBFeedbackOnApplicationModule();
         throw new JboException(e);
      else
     ....................................Now it should work. Your application will gracefully handle the errors, and once that is done, you just throw an exception in order not to commit.
Regards
Luc Bors