ADF Error Handling Options

Question

JDeveloper 11.1.1.5
I'm tring to handle errors to avoid showing java stack trace, SQL, and instead show user friendly messages.
(A) To handle errors in the model layer I setup DataBindings.cpx by I adding as ErrorHandlerClass="package.MyDCErrorHandler" that extends DCErrorHandlerImpl.
Inside MyDCErrorHandler I simply log the exception then throw a new JBO exception with a generic "Unhandled error call customer support" message instead of the exception message.
(B) On the task flow I created a method and marked it as exception handler as descibed here.
http://andrejusb.blogspot.com/2011/03/exception-handler-for-method-calls.html
http://andrejusb.blogspot.com/2011/03/exception-handler-for-method-calls_19.html
I do similar logic here, log the exception then show generic faces message "Unhandled error call customer support"
Is this a good methodolgy?
This seems to work fairly well but ocassionaly an exception slips through and shows default error message.
I'm now looking at this option
http://blogs.oracle.com/jdevotnharvest/entry/extending_the_adf_controller_exception_handler
How does this compare to extending DCErrorHandlerImpl(A) and task flow exception handler method(B)?
I note that this option uses Throwable instead of Exception. Will this handle java errors (like OutOfMemory)?

Answer 1

Hi,
I'm now looking at this option http://blogs.oracle.com/jdevotnharvest/entry/extending_the_adf_controller_exception_handler How does this compare to extending DCErrorHandlerImpl(A) and task flow exception handler method(B)? I note that this option uses Throwable instead of Exception. Will this handle java errors (like OutOfMemory)?
Actually the default ADFc Exception handler does not listen for all kind of exceptions but only those that can be handled by the controller. If you have an exception that is not handled by the ADFc exception handler then you can take a chance and handle this in your own exception handler class. You would handle the specific exception you are interested the most to handle and re-throw all the rest for the ADFc controller to try and handle.
Just create a custom handler and print the exceptions you receive in there. If this prints the OOM error then you can handle it. If it isn't shown here then you cannot handle it this way
Frank