[
https://issues.apache.org/jira/browse/SLING-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Klimetschek updated SLING-571:
----------------------------------------
Attachment: SLING-571-reloaded.patch
A second patch that tries to provide a full exception chain by unpacking
ServletException and fetching the rootCause.
Background: ServletExceptions do not use the normal "cause" of exceptions
(which is used for exception chaining, ie. when printing the full stacktrace),
but introduce their own "rootCause" member. So once an exception chain comes to
a ServletException, it effectively stops.
> JspServletWrapper swallows jsp exceptions if root cause is null
> ---------------------------------------------------------------
>
> Key: SLING-571
> URL: https://issues.apache.org/jira/browse/SLING-571
> Project: Sling
> Issue Type: Bug
> Components: Scripting JSP
> Affects Versions: Scripting JSP 2.0.2
> Reporter: Tobias Bocanegra
> Assignee: Carsten Ziegeler
> Fix For: Scripting JSP 2.0.4
>
> Attachments: SLING-571-reloaded.patch, SLING-571.patch
>
>
> For example for a JSP compile error the 'realException' is null and the
> following stack-frame resolution fails:
> (JspServletWrapper.java, line 492ff)
> // First identify the stack frame in the trace that represents
> the JSP
> StackTraceElement[] frames = realException.getStackTrace();
> StackTraceElement jspFrame = null;
> for (int i=0; i<frames.length; ++i) {
> if (
> frames[i].getClassName().equals(this.getServlet().getClass().getName()) ) {
> jspFrame = frames[i];
> break;
> }
> }
> Suggest to check for (realException == null)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
