Well, that’s easy-- you already have a try/catch wrapped around the runEvent that runs the custom exception handler with a “Error Running Custom Exception handler” log in the catch. Just add a second log in the catch to ensure that the original ExceptionBean gets logged as well since the exceptionHandler ran into problems.
That way, if the custom exception handler is working, it can have the option to log the error. Otherwise, if the custom exception handler itself errors, the framwork will go ahead and log the original error just in case, and then log error the exception handler threw as well.
Luis, did you ever come to a decision on this one?
Did my solution below to give me back the original functionality I
desire while still addressing your concern make sense?
If it helps my case, I'd like to point out that the latest
functionality breaks with the old documentation that states this:
"No error is logged automatically by ColdBox since you are using the
custom exception handler. Therefore, you must do EVERYTHING!!" http://wiki.coldbox.org/wiki/Recipes:My_First_Custom_Exception_Handler.cfm
