[
https://issues.apache.org/jira/browse/SLING-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062858#comment-13062858
]
Carsten Ziegeler commented on SLING-2094:
-----------------------------------------
Thanks for your feedback, Antonio,
For the exception I see three solutions:
a) we find the place where it gets wrapped and avoid it
b) we unwrap exception and look if one of the wrapped exceptions is a
SlingPageException
c) we use the request attribute approach
I would like to avoid c) and also b) - if this happens which exception type is
wrapping the SlingPageException?
> 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/users@sling.apache.org/msg01369.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
