On 1:59 PM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Manuel,
On 4/5/12 11:42 AM, manuel aldana wrote:
Inside web.xml I defined500..., so 500-status is
resolving to JSP error pages. I get inconsistent behaviour when an
Exception occurs during JSP rendering.
1)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Manuel,
On 4/5/12 2:47 PM, manuel aldana wrote:
> Inside JSP we have a backing model, which contains the dynamic data
> to be displayed inside JSP. Itself the model is held quite simple,
> but due to programming errors it can happen, that null-referen
Am 05.04.12 18:07, schrieb Christopher Schultz:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Manuel,
On 4/5/12 11:42 AM, manuel aldana wrote:
Inside web.xml I defined500..., so 500-status is
resolving to JSP error pages. I get inconsistent behaviour when an
Exception occurs during JSP renderi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Manuel,
On 4/5/12 11:42 AM, manuel aldana wrote:
> Inside web.xml I defined 500..., so 500-status is
> resolving to JSP error pages. I get inconsistent behaviour when an
> Exception occurs during JSP rendering.
>
> 1) JSP syntax error (e.g. broken XM
Inside web.xml I defined 500..., so 500-status is resolving
to JSP error pages. I get inconsistent behaviour when an Exception
occurs during JSP rendering.
1) JSP syntax error (e.g. broken XML):
===
-> 500 status is set correctly
-> forward to jsp-error page is done correctly and 500 returned t
