[
https://issues.apache.org/jira/browse/SLING-2094?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-2094.
-------------------------------------
Resolution: Fixed
Many thanks again for your patch, Antonio!
I've applied my slightly modified version together with the test case in
revision 1145904.
The test cases did not succeed as the error page jsp has the isErrorPage="true"
directive which in turn automatically sets the status code of the response to
500. This is clearly not desirable in the case of Sling - therefore I removed
this automatic setting of the status code.
> 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