ADF: Gracefully handling JDBC connection errors? Part II

Question

Hi gang
I while back I posted a forum post to find a solution to "display a specific web page when the JDBC connection drops out on our ADF application, specifically the following error: oracle.jbo.DMLException: JBO-26061: Error while opening JDBC connection"
...you can see the original post here:
Re: ADF: Gracefully handling JDBC connection errors?
For the life of me I can't get this to work now. It appears I can't redirect to another page during the call to reportException. I've had a play with different methods of redirecting, as seen in the following code sample:
public class ErrorHandlerImpl extends DCErrorHandlerImpl {
  public ErrorHandlerImpl() {
    super(true);
  @Override
  public void reportException(DCBindingContainer dCBindingContainer, Exception exception) {
//    try {
      String message = exception.getMessage();
      if (message.indexOf("JBO-26061") >= 0) {
        // Method 1
        FacesContext fc = FacesContext.getCurrentInstance();
        UIViewRoot viewRoot =
        fc.getApplication().getViewHandler().createView(fc, "faces/errorPage.jspx");
        fc.setViewRoot(viewRoot);
        fc.renderResponse();
        // Method 2              
        // FacesContext fc = FacesContext.getCurrentInstance();
        // fc.getApplication().getNavigationHandler().handleNavigation(fc, null, "goError");
        // fc.responseComplete();
        // Method 3 - required IOExcepition handler
        // FacesContext.getCurrentInstance().getExternalContext().redirect("faces/errorPage.jspx");
      } else
          super.reportException(dCBindingContainer, exception);
//    } catch (IOException e) {
}... with no success.
Has anyobody any other solutions or advice on getting this to work?
Your help appreciated.
Thanks & regads,
CM.
PS. JDev 11gR1 ADF BC + ADF Faces RC

Answer 1

Hi Frank
Yep, I' tried redirect, that was method 3 (you can see all 3 methods I've attempted, last 2 are commented out).
With the declarative ADFc exception handler, problem is it's a catch all, not specifically for JBO-26061. Can you think of a way I can tailor fit it for JBO-26061 with a custom message "Database down"?
In addition the exception handler is not consistently called. As example, if you're moving between pages rather than operating on 1 page, the standard af:messages error dialog is shown if the db connection has been dropped, rather than navigating to the exception handler page. As such it seems the DCErrorHandlerImpl.reportExceptions is the better chokepoint to work from.
Cheers,
CM.