[
https://issues.apache.org/jira/browse/SLING-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044946#comment-13044946
]
Carsten Ziegeler commented on SLING-2094:
-----------------------------------------
I think propagating the exception to the top of the jsp engine is fine - this
avoids cluttering too much in the jasper code.
I think, if we restrict the errorPage to a jsp page, you should be able to get
the jsp page by path - if you look at the method
JspScriptEngineFactory#getJspWrapperAdapter: the jsps is created/fetched by
resource path, so using this approach, it should be easy to call any other jsp
from within the jsp scripting without going through the resource resolver or
the script resolver.
> 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: Engine, Scripting
> Reporter: Antonio Sanso
> Priority: Minor
> Attachments: SLING-2094-asanso-patch.txt, SLING-2094-asanso2-patch.txt
>
>
> 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
