JD3.2: DACF: Error distribution

Question

I am trying to process errors which arise when user tries to commit empty value for NOT NULL column in GridControl. I successfully intercept DAC-603 error and handle it. But, there are actually two errors raised in response of this user action: one from Client Framework (DAC-307) and another from Server Framework (DAC-314). I can process the first one and just veto another. No problem... in this case.
However, from this example I see that I don't understand the mechanism of DACF error distribution. Particularly, I want to know:
1. What is the difference between Client and Server frameworks in terms of DACF error messages? Does it reflect separation into InfoSwing components and InfoProducers?
2. Where do these frameworks take information about NOT NULL constraints from?
3. Why the Client Framework passes the information to Server Framework while it knows that information is invalid? Can I prevent it?
I didn't find anything about it in JD 3.2 documentation.

Answer 1

Adam,
I retrieved information about error processing from the following sections of JD3.2 documentaion:
1. Developing Data Forms for Business Components->
Programming the Data Form Client Runtime->
Retrieving Error Message Object Information in Data Forms
2. 1. Developing Data Forms for Business Components->
Programming the Data Form Client Runtime->
Using the Provided Error Loggers in a Data Form
3. Reference for oracle.dacf.util.errormanager and oracle.dacf.util.errorloggers APIs.
Here are snippets from my error processing code. ClassesEditor is a modal dialog which attaches its own ErrorManagerListener to ErrorManager when gets activated and removes it before closing. Editor consists of single DACF GridControl. ErrorParser is a utility class for retrieving concatenated error description. Its method was taken from the thread 'About JBO messages and DacfErrorMessageContext'.
class ClassesEditor extends JDialog
private void jbInit() throws Exception
this.addWindowListener(new java.awt.event.WindowAdapter()
public void windowClosing(WindowEvent e)
processWindowClosing(e);
public void windowActivated(WindowEvent e)
processWindowActivated(e);
private void processWindowClosing(WindowEvent e)
ErrorManager.removeErrorManagerListener((new ErrorHandler()).getName());
void processWindowActivated(WindowEvent e)
try {
ErrorManager.addErrorManagerListener(new ErrorHandler());
catch(NameAlreadyRegisteredException exception) {
private class ErrorHandler implements ErrorManagerListener
public void addingErrorMessage(ErrorMessage message)
throws oracle.dacf.util.errormanager.ErrorMessageVetoException
String errorMessage=ErrorParser.getJboErrorMessageStack(message);
if(errorMessage.indexOf("ORA-00001")!=-1)
JOptionPane.showMessageDialog(ClassesEditor.this,
"Class name should be unique", "Error",
JOptionPane.ERROR_MESSAGE);
else if(errorMessage.indexOf("DAC-603")!=-1)
//catch the client error, ignore the similar server one
if(message.getMessageText().getId().toString().equals("DAC-307"))
JOptionPane.showMessageDialog(ClassesEditor.this,
"Class name should not be empty", "Error",
JOptionPane.ERROR_MESSAGE);
else
return;
throw new ErrorMessageVetoException("Error processed. "+getName());
public String getName()
return "Class editor's error handler";
public void removingErrorMessage(ErrorMessage parm1)
throws oracle.dacf.util.errormanager.ErrorMessageVetoException
public void rollingBackAddingErrorMessage(ErrorMessage parm1)
public void rollingBackRemovingErrorMessage(ErrorMessage parm1)
import oracle.dacf.util.errormanager.*;
import oracle.dacf.dataset.*;
import oracle.jbo.*;
public class ErrorParser
** Walk through JBO error stack and create a concatenated
error message.
** @return JBO error message
public static String getJboErrorMessageStack(ErrorMessage em)
StringBuffer returnvalue = new StringBuffer();
ErrorMessageContext context=em.getErrorMessageContext();
if(context!=null && context instanceof DacfErrorMessageContext)
if(((DacfErrorMessageContext)context).getException()
instanceof DacfRuntimeException)
Exception origException=((DacfRuntimeException)
((DacfErrorMessageContext)context).getException()).
getOriginalException();
if(origException!=null)
returnvalue.append(origException.getMessage());
Object [] details = null;
if(origException instanceof JboException)
details=((JboException)origException).getDetails();
if(details!=null && details.length>0)
for(int i=0;i<details.length;i++)
if(details[i] instanceof JboException)
returnvalue.append("\n");
returnvalue.append(((JboException)details).getMessage());
else if (details[i] instanceof Exception)
returnvalue.append("\n");
returnvalue.append(((Exception)details[i]).getMessage());
return returnvalue.toString();
Thi s code works well. However, one still has to empirically discover all possible errors in application and incrementally add custom error processing code. It would be nice to have some error management patterns based on various popular constraints like NOT NULL and UNIQUE. In any case, DAC error messages reference would be helpful.
Hope this helps,
Vladimir
null