[
https://issues.apache.org/jira/browse/SLING-11299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-11299.
--------------------------------------
Resolution: Fixed
Fixed in
https://github.com/apache/sling-org-apache-sling-scripting-jsp/commit/0d8ae29e38af946efe555c2da0ef82230efc0656
In order to get the compiler information, the JSP is compiled on demand if an
exception occurs
> JSP source/linenumber is not always shown when an exception occurs
> ------------------------------------------------------------------
>
> Key: SLING-11299
> URL: https://issues.apache.org/jira/browse/SLING-11299
> Project: Sling
> Issue Type: Bug
> Components: Scripting
> Affects Versions: Scripting JSP 2.5.4
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: Scripting JSP 2.5.6
>
>
> If the JSP engine is just loading an already compiled JSP, all the compiler
> information is not available. Therefore when an exception occurs, the correct
> source/line number of the JSP can't be displayed.
> In addition, the whole handling and wrapping/unwrapping of exceptions looks
> far too complicated
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
