Server errors result in blank pages with security enabled

Question

I have been working to security-enable my ADF 11 application using JDeveloper 11.1.1.0.0. Users, roles and grants all appear to be working as expected. However, I have discovered that server errors no longer appear once I put security in place.
For example, take a simple JSPX page with one button, and attach an actionListener to the button. In the actionListener, throw an exception. When no ADF security is in place, this results in a 500 server error page, and the exception stack trace (or part of it) is written to the Weblogic console inside JDeveloper. Once ADF security is in place, the behavior changes. The result is a blank page (absolutely no content). Even worse, the exception stack trace is no longer written to the Weblogic console.
I have tried to work around this by setting an <error-page> in web.xml, but it doesn't seem to make a difference. I do know that my <error-page> configuration works in general, because I have a "not authorized" error page set up to catch the ADF AuthorizationException, and that is displayed properly. I have also seen the error page invoked for errors that happen earlier in the rendering process (for instance, if I forget to set a default page in my bounded task flow).
I don't have any idea where to start on this. Google hasn't been much help, possibly I don't know what I'm looking for.
Anyone have any suggestions?
Thanks,
KEN

Answer 1

We have found a solution to this problem, which we are going to go with until something better pops up.
In the main unbounded task flow (adfc-config), we added a method call marked as the error-handler. In the method call, we log the exception, something like this:
    public void handleException() {
        Exception e = ControllerContextImpl.getInstance().getCurrentViewPort().getExceptionData();
        e.printStackTrace(System.err);
    }Then, the method call forwards to a JSP to display the error:
<af:inputText label="Error" value="#{controllerContext.currentViewPort.exceptionData.message}"/>That gets us the equivalent of the old behavior.
I still find it kind of strange that errors aren't displayed once security is enabled, but at least there is a workaround.
KEN