after a bit more digging... if you only have the errorPage directive in
the enclosing page, the error that is reported is the error thrown by
the tag that calls the errant (included / inserted) sub page. So in
order to get the root cause error you need the errorPage directive in
every jsp.
Na
if enclosing page (e.g. tiles layout) forwards to or includes a jsp that
throws an error (compile or otherwise) and the enclosing page doesn't
have the errorPage directive, the sub-page processing of the error page
causes an IllegalStateException (see bottom of email)
result being the enclosin
On Sun, 16 Jan 2005 12:10:37 +0800, Nathan Coast <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I've been strugling for a while with exception handling. I've been
> trying to ensure:
> 1) all exceptions are displayed consistently regardless of where / how
> the exception is raised.
> 2) the root cause exce
Hi,
I've been strugling for a while with exception handling. I've been
trying to ensure:
1) all exceptions are displayed consistently regardless of where / how
the exception is raised.
2) the root cause exception is always displayed,
I'm not saying this is the best solution, nor even a 'correct
4 matches
Mail list logo
