Preventing an OperationBinding from putting messages into the FacesContext

Question

Hi,
We sometimes manually execute an OperationBinding by calling something like:
OperationBinding op = bindings.getOperationBinding("someOperation");
op.execute();Sometimes the facade method that gets called throws an exception. It's a useful exception containing a useful description of the problem. We can extract the necessary information from the exception and display it to the user via a FacesMessage.
Here's the problem: the OperationBinding.execute() method stuffs the FacesContext with gibberish messages that look similar to this:
JBO-29000: Unexpected exception caught: javax.ejb.EJBException, msg=java.lang.IllegalArgumentException: ........... .; nested exception is: java.lang.IllegalArgumentException: ............Such messages are completely unacceptable to appear in the GUI. We need to put a user-friendly message instead.
So, how can we prevent ADF from stuffing the FacesContext with gibberish messages? Or, if it's impossible to prevent these messages, could anyone, please, advise how we can remove them from the context?
Thanks in advance.

Answer 1

Actually, Wes' post indicates how to create a custom error handler - the error handler is responsible for looking at the exceptions generated and converting them to Faces messages.
OperationBinding's execute() method, when exceptions occur in the underlying method, wrap the exception inside things like JBO-29000 (as you've seen). You could very well take Wes' approach, create a custom error handler, and when you get a JBO-29000, walk the exception details yourself and only add Faces Messages as meet your requirements (i.e., don't add a message for the JBO-29000).
Ideally, I'd like a way to do something like this (hint hint hint to Oracle), which cannot be done today:
OperationBinding op = something;
try
  op.executeButPleaseDontEatTheExceptionsAndJustThrowThem();
catch (MyCustomException mce)
}As to Jags' post - the messages still display.
John