[
https://issues.apache.org/jira/browse/SLING-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13044898#comment-13044898
]
Antonio Sanso commented on SLING-2094:
--------------------------------------
Thanks for the feedback Carsten. Point taken. I'll provide a new patch
implementing this strategy. Couple of comments though.
The patch provided:
-if no errorPage is defined everything works as today
- if an errorPage is defined a Runtime error is thrown and propagated. This
solution mimics the current implementation (see the other RuntimeExceptions in
the jsp module) and allow to resolve the resource defined in the errorPage as a
Sling resource. My question is: is it possible achieve the same without
propagating the exception. If not is it possible at least to call the errorPage
(if it is under the sling domain) inside the jsp bundle?
> 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
