[
https://issues.apache.org/jira/browse/SLING-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13063557#comment-13063557
]
Antonio Sanso commented on SLING-2094:
--------------------------------------
thanks a lot for the comment Carsten.
After deeper investigation I actually think that the SlingPageException below
is never caught due different Classloader context (or at least if what it was
my conclusion after seen that even if a SlingPageException has been thrown it
is never cought from the right catch statement- it always goes to the last
namely Exception).
handleJspException(ex);
} catch (IllegalStateException ex) {
handleJspException(ex);
} catch (SlingPageException ex) {
handleJspException(ex);
}catch (Exception ex) {
handleJspException(ex);
}
> Adding support to call a sling resource for JSP page exception handler <%@
> page errorPage ... %>
> -------------------------------------------------------------------------------------------------
>
> Key: SLING-2094
> URL: https://issues.apache.org/jira/browse/SLING-2094
> Project: Sling
> Issue Type: New Feature
> Components: Scripting
> Reporter: Antonio Sanso
> Assignee: Carsten Ziegeler
> Priority: Minor
> Fix For: Scripting JSP 2.0.18
>
> Attachments: SLING-2094-asanso-patch.txt,
> SLING-2094-asanso2-patch.txt, SLING-2094-asanso3-patch.txt,
> SLING-2094-asanso4-patch.txt, SLING-2094-integration-tests.patch,
> scripting.patch
>
>
> At the moment the JSP page exception handler (<%@ page errorPage ... %>) is
> not supported as the jsp engine can't resolve the path to the jsp if this is
> a repository resource.
> See also the user mailing list [0] for more details
> [0] http://www.mail-archive.com/[email protected]/msg01369.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
