[
https://issues.apache.org/jira/browse/SLING-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-111.
-----------------------------------
Resolution: Fixed
Removed the Jasper source from the repository and adapted the JSP scripting
support accordingly.
This has the following consequences:
* Java source and class files for JSP scripts are stored in the file system
* Any resources used by the JSP compiler through the ServletContext of the
compiler
are accessed through the ResourceResolver of the request being
processed.
> Remove local Jasper copy and use standard Jasper
> ------------------------------------------------
>
> Key: SLING-111
> URL: https://issues.apache.org/jira/browse/SLING-111
> Project: Sling
> Issue Type: Bug
> Components: JSP
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> Currently we have a local copy of Jasper 5.5 with patches to write Java
> classes into the JCR repository in our source tree. This virtually prevents
> us from keeping up to date with more recent versions of Jasper and also
> duplicates code (from the original Jasper code).
> Class need - for the moment - not be stored in the repository any more and so
> we may remove the Jasper code and use the standard Jasper build to write the
> classes to the local file system.
> A canonical location for the classes must be found an documented.
> [1] http://markmail.org/message/ud4tlcbm53bxj7vd
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
