[
https://issues.apache.org/jira/browse/SLING-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-116.
-----------------------------------
Resolution: Fixed
Fixed in Rev. 599941:
- Bring back the RepositoryIOProvider, slightly modified
- Make use of ResourceResolver to read resources using request user
session
- Always write to the rpository using administrative session
- Add patched Jasper 6.0.14, using the same path as reported for Tomcat bug
43979
but refactored below the org.apache.sling.scripting.jsp package
Now JSPs are compiled to the repository and executed from within the repository
again.
> Add support for compilation into the respository again
> ------------------------------------------------------
>
> Key: SLING-116
> URL: https://issues.apache.org/jira/browse/SLING-116
> Project: Sling
> Issue Type: Improvement
> Components: JSP
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> My message [1] on the list prompted quite some reactions ..... So I decided
> to forward port the patches I applied to Jasper 5.5.20 to Jasper 6 trunk and
> report a bug to tomcat for its inclusions [2].
> At the same time, I applied the patch to the 6.0.14 tag of Jasper and added
> it to the scripting/jsp project again, this time refactored below the
> o.a.s.scripting.jsp package as an intermediate solution.
> When Tomcat decided to include my patch, we can revert back to using the
> official Jasper build, at which time of course all JSP must be recompiled,
> which is probably not that big a problem.
> [1] http://www.mail-archive.com/[email protected]/msg00995.html
> [2] http://issues.apache.org/bugzilla/show_bug.cgi?id=43979
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
