Yes, I still think it is inconsistent behaviour (error page should be transparent, whether user threw a checked or an unchecked exception himself).
Even worse, when using exception-chaining it happens that unchecked application exception is not shown at all and is being swallowed (see screenshot uncheckExceptionSwallowedIfChainingUsed.png).
I tend to use unchecked exception in my application and use exception chaining a lot. I remember that I was quite confused that my application exception did not show up on the error page.
Reason seems to be that first top-level exception is filtered in error page. The easiest fix was to use this last RuntimeException wrap.
Is this fix really an issue? What speaks against it?